| 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
| ||||
| ||||
Hello, I have dual VIO servers using MPIO to a SAN. I created the devices on the vio server using the mkvdev command. What is strange though is the order of the disks on the lpar does not match the LUN number order. In other words, hdisk3 might be LUN 61 and hdisk4 might be 60 (this is the L60 number that shows up on lscfg -l hdisk4 on the LPAR). If I remove all the hdisks with rmdev -dl hdisk3 (same for hdisk4), they will recreate in the same order. What controls the order of disk discovery with VIO disks? |
|
#2
| ||||
| ||||
AIX used to assign hdisk numbers based on the order in which the drives were discovered. Then the hdisk number was stored in the OD with the location code of the devices, this is why hdisks often differed from what is seen in SMS. The best I have been able to figure with MPIO is that this process still holds true. If you have patience and time you could go through and change your hdisk numbers but it is often not worth the effort. You can easily cross reference the HDISK numbers to serial number and then write a script or use excel to cross reference this to corresponding hdisk numbers for the two VIO servers. Having a developed process for doing this will aid in long term supportability of your servers. |
|
#3
| ||||
| ||||
What you can do more easily .... mkvdev on VIO the first LUN cfgmgr on the LPAR -> hdiskx mkvdev on vio the second LUN cfgmgr on the LPAR -> hdiskx+1 etc. etc. etc. its a bit more work but in the end you got the disks like you want to Dont forget to delete the disks on the LPAR before you begin as it numbers new disks from the last it detected (lsdev |grep hd) to see you disks |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Microsoft Windows 2003 Active Directory integration | FASherman | Tutorials | 25 | April 28th, 2008 07:14 |
| Adding additional MPIO disks | kshow | AIX for POWER Systems | 3 | August 3rd, 2007 00:21 |
| Setting up MPIO | ketse | Hardware Management Console | 6 | May 19th, 2007 07:27 |