Blogs Classifieds Downloads FlashChat Gallery Googlemap Invite Friends Links Projects Reviews Wiki
 


Welcome to the pSeries Tech Forums, our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software.

You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments.

Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community.

Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Our Sponsors
Want to advertise?  


Reply
 
LinkBack Thread Tools
  #1  
Old March 25th, 2008
mlewis's Avatar
mlewis Offline
Junior Member
 
Join Date: November 2006
Posts: 13
Virtualized disk mapping

All does anyone have an easy way to establish which disks are mapped to which client.? I am using a p570 with 2 vio servers obviously using virtual SCSI. I am attempting to marry up the PVIDS but this does'nt work? any ideas welcome.

thanks Martin
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #2  
Old March 25th, 2008
donzg's Avatar
donzg Offline
Junior Member
 
Join Date: May 2007
Location: Los Angeles
Posts: 1
Re: Virtualized disk mapping

From the vio server just run lsmap -all. You should be able to see what slot is assigned to what client. When I run the mkvdev command I usually assign the -dev with the servername to make it a lot easier to identify what disk is assigned to what server.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #3  
Old March 31st, 2008
kah00na's Avatar
kah00na Offline
Junior Member
 
Join Date: October 2006
Posts: 15
Re: Virtualized disk mapping

Here is a short script that will give you the hdisk# and the mapping name (-dev) that was assigned to it:

Code:
su - padmin -c 'ioscli lsmap -all' > /tmp/lsmap.out
for disk in $(lspv | grep -v rootvg | awk '{print $1}'); do
        echo "${disk} - \c"
        echo "$(egrep -p "Backing device        ${disk}$" /tmp/lsmap.out | grep ^VTD | awk '{print $2}')"
done
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #4  
Old March 31st, 2008
kah00na's Avatar
kah00na Offline
Junior Member
 
Join Date: October 2006
Posts: 15
Re: Virtualized disk mapping

That script makes a couple of assumptions...
1. Your VIO server has its rootvg is on internal disks and, therefore, won't have mappings.
2. When you created your mappings you used the "-dev" option to give it a particular label.
3. The script also needs to run as root (oem_setup_env).
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
  #5  
Old March 31st, 2008
ross.mather's Avatar
ross.mather Offline
Senior Member
 
Join Date: January 2007
Location: Nomadic in the UK
Posts: 394
Re: Virtualized disk mapping

Try and avoid using the oem_setup_env command if you can - it may be deleted someday. That said you frequently have no choice at this stage - if you have a DS4000 series you need to be able to run fget_config to work out which LUN is which.

This script will work in pronciple from any server you have if you have ssh installed on the VIO server - which is now done as standard.

In my view the most important thing in maintaining disk mappings is to have structure in your slot ids, so that you can trace things. I always enable the pvid on all disks in a VIO.

Everything gets confusing as you have Server SCSI slots which map to Client SCSi slots and generate a vhost on the VIO Server. To that you cannect an hdisk with a pvid and you get a vscsi at the end. Are you confused yet? You should be - I've seen people tie themselves in knots over this.

The most reliable method of checking is to verify the pvid against the Server slots that are connected to an LPAR. pvid at the VIO level are the same as pvs at the LPAR level if you have connected LUNS through the VIO directly to an LPAR.
__________________
Ross Mather, IBM AIX IT Specialist.
That said anything I say here is my own opinion and not anything that you can ever hold against IBM.
Ohhh and don't forget that I make mistakes too....
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Reply

Bookmarks

These are the 100 most searched terms
Search Cloud
0042-001 0042-001 nim 0513-001 the system resource controller daemon is not active 0513-001 the system resource controller daemon is not active. 0514-061 0514-061 cannot find a child device 0514-061 cannot find a child device. 0516-787 0516-787 extendlv 0516-787 extendlv: maximum allocation for logical volume 110000ac aa00e1f3 aio aix aix aio aix freeware aixif_arp_dup_addr b150f22a b181fb53 ba010004 c1001020 d133c002 dacnone dcb47997 dlpar fcp_array_err6 fget_config gnu tar aix gsclvmd gtar aix hi yall hmc root password hmc vmware hscl05db ibm p6 ibm p6 520 libpopt aix libpopt.a libpopt.a(libpopt.so.0) is needed by rsync-2.6.2-1 migratelv mksysb navisphere agent nim server pseries pseriestech rsync aix sc_disk_err4 scan_error_chrp vio server websm xhost file ... powered by Simple Search Cloud


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Powered by vbWiki Pro 1.3 RC5. Copyright ©2006-2007, NuHit, LLC

vBulletin Skin developed by: vBStyles.com


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48