Sponsored Content
Full Discussion: LPAR and vio disk mapping
Operating Systems AIX LPAR and vio disk mapping Post 302278895 by dknell on Wednesday 21st of January 2009 11:55:46 AM
Old 01-21-2009
There are a number of configurations and ways to figure out which VIO server is presenting a disk to an LPAR. Hopefully the instructions below will at least point you in the right direction.

If you are not using MPIO on the client side (LPAR), you can track down a physical disk (or LUN) by using the Physical Location code (Physloc) by running the following commands:

on the client LPAR (assuming you want to find hdisk0) run this command:
lscfg -l hdisk0 -vps
You will see a line similar to this:
hdisk0 U8204.E8A.xxxxxxx-V5-C21-T1-L810000000000
The number after 'C' is the slot for the Virtual Adapter that you assigned on your HMC - in this case it is 21. You will also see this number on your HMC.

on your VIO server(s) run this command as padmin:
lsmap -all
You will see lines similar to these:
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U8204.E8A. xxxxxxx-V2-C21 0x00000005

The C21 means that this VIO server is presenting the disk to your LPAR (also take note of the Client Partition ID - you can also run lparstat -i on your client LPAR to verify that it is correct)

Now, one thing to keep in mind is that you can assign the same Virtual Adapter slot number on BOTH VIO servers - for example C21 can be assigned to the same LPAR from both VIO1 and VIO2. If that is the case then you are probably using MPIO on your LPARs.

to find out if you are using MPIO run lspath on your LPARs. If you see more than one vscsi device for the same hdisk, then you are using MPIO. To find the current active path to your VIO server, run the following command from your LPAR:
for i in `lspath -l hdisk0 -F"parent"`; do lscfg -vl $i; done
you will see the C## slot numbers again, which can be used to track the disk back to you VIO server using the lsmap -all command I described above.

I hope this helps.

Dave
This User Gave Thanks to dknell For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

Help urgent : vio server - add extral disk on virtual lpar

Hi, I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7). I extend my vg vg000 (on the partition) and add the 2 hdisks. I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies

2. AIX

Restoring mksysb to vio lpar?

I have a standard template I deploy for each of my AIX servers. It's in a mksysb format which I pulled via the nim server after I originally set it up. I'm trying to restore this mksysb over the wire to a remote system. The remote system is an lpar running under vio (no HMC attached). The disk... (1 Reply)
Discussion started by: scottsl
1 Replies

3. UNIX for Dummies Questions & Answers

Unix VIO vs Dynamic LPAR

Can you have a Dynamic LPAR without VIO and if yes is there a benefit to having both? I am attempting to implement VIO and Resource pooling at my company and want to understand the limitations. Also, I have been told the managing and allocation of the Logical Volumes is a time consuming task as... (0 Replies)
Discussion started by: bombers73
0 Replies

4. AIX

Problem mapping LUN disk from VIOS to the LPAR

Hello guys, It would be so nice of you if someone can provide me with these informations. 1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies

5. AIX

VIO Backing Disk LPAR how to find which one ?

hello Folks, my vio: $ lsmap -all SVSA Physloc Client Partition ID --------------- -------------------------------------------- ------------------ vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003 VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies

6. AIX

LPAR and AIX VIO Disk Mappring for Linux Clients

VIO Server is managing both AIX Clients and Linux Clients. For AIX Clients, we could do a disk mapping from slot numbers to VIO and also uname -L to determine the lparid and serial number frame its running on. From a Linux Client, How do I know which IBM frame its running on? Any command to... (4 Replies)
Discussion started by: rpangulu
4 Replies

7. AIX

LPAR - What is my VIO (hostname, IP, ...)

I am wondering if there is a command I can run from **with-in** LPAR server (server01) to find out the hostname or IP address or other parameters for VIO server in charge of server01? (1 Reply)
Discussion started by: ms1232
1 Replies

8. AIX

Possible to connect a LPAR to two different VIO's?

Just a question which may seem dumb to some out there, but then again I am not a super technie so that's my excuse. Is it possible to say provision a test AIX LPAR (has a 10gb boot lun and 20gb data) under a VIO which has connectivity to SAN Array A so it can see the disks provisioned to it,... (2 Replies)
Discussion started by: Johnny1314
2 Replies

9. AIX

VIO server does not show new LPAR

Hi All, I've been trying to create a new LPAR for some days now but I can't get the VIO server to recognize the new LPAR. This is what I did: On HMC create new LPAR On HMC create new virtual scsi adapter for LPAR in VIO profile On HMC add new virtual scsi adapter for LPAR with DLPAR... (6 Replies)
Discussion started by: petervg
6 Replies

10. AIX

VIO and LPAR disk/fcs communications

:wall::wall::wall: 1. I have created an LPAR in the HMC. 2. I have allocated the storage from an Hitachi AMS2500 and assigned it to the host group. 3. I have zoned the LPAR and Storage on a Brocade 5100. (The zone sees the AMS) Next I activated the LPAR in the HMC, SMS mode for the mksysb... (3 Replies)
Discussion started by: Dallasguy7
3 Replies
GNOME-DISK-IMAGE-MOU(1) 					gnome-disk-utility					   GNOME-DISK-IMAGE-MOU(1)

NAME
gnome-disk-image-mounter - Attach and mount disk images SYNOPSIS
gnome-disk-image-mounter [--writable] [URI...] DESCRIPTION
gnome-disk-image-mounter can be used to set up disk images. Both regular files and GVfs URIs (such as smb://filer/media/file.iso) can be used in the URI parameter. If no URIs are given and a window server is running, a graphical file chooser will be presented. Note that gnome-disk-image-mounter will not mount filesystems or unlock encrypted volumes in the disk image - this responsibility is left to the automounter in GNOME Shell to ensure that the same interactions happen as if the disk image was a regular physical device or disc. By default the disk images are attached read-only, use the option --writable to change this. RETURN VALUE
gnome-disk-image-mounter returns 0 on success and non-zero on failure. AUTHOR
Written by David Zeuthen <zeuthen@gmail.com> with a lot of help from many others. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-disk-utility. SEE ALSO
gnome-shell(1), gnome-disks(1), udisks(8), losetup(8) GNOME
March 2013 GNOME-DISK-IMAGE-MOU(1)
All times are GMT -4. The time now is 09:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy