| 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? | |
![]() |
| | LinkBack | Thread Tools |
|
#1
| ||||
| ||||
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 |
|
#2
| ||||
| ||||
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. |
|
#3
| ||||
| ||||
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
|
|
#4
| ||||
| ||||
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). |
|
#5
| ||||
| ||||
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.... |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |