Comments (5)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 lpuname commented Permalink

Excellent Article, this helps to understand to some extent to trace back PV in LPAR to VIO, <div>&nbsp;</div> I'd would appreciate if you could share us more details on HOW can we easily tell LUN details to storage team which had been presented through VIO to LPAR. Thanks

2 AnthonyEnglish commented Permalink

Thanks for the encouragement. <div>&nbsp;</div> About your question, it's a good deal easier to trace LUNs when you're using NPIV adapters and virtual fibre channel adapters. The LUNs on the VIO client have a unique WWPN which can be seen from the SAN. <div>&nbsp;</div> As for vscsi devices, that's a bit more work, but from the VIO server, the chkdev command (only since VIOS 2.1 FP 22.1) is helpful. See Chris Gibson's post: https://www.ibm.com/developerworks/mydeveloperworks/blogs/cgaix/entry/the_new_chkdev_command_for_vios_2_1?lang=en <div>&nbsp;</div> On the VIO client, you can get the PVID and unique id using lsattr -El hdiskN <div>&nbsp;</div> I've recently found this command useful to display the unique id so you can match it up to the SAN LUN ID: <br /> odmget -q name=hdiskN attribute=unique_id CuAt <div>&nbsp;</div> There's more on this especially in chapter 2 of the Migration from Physical to Virtual redbook: <br /> http://www.redbooks.ibm.com/redbooks/pdfs/sg247825.pdf <div>&nbsp;</div> I plan to do a more complete post on mapping LUNs from the VIO client to the VIO server to the SAN, but I will need to work in a couple of environments to provide some decent examples.

3 nostrum commented Permalink

I tried the command "odmget -q name=hdiskN attribute=unique_id CuAt" in comments 2 and got this error info: <br /> 0518-506 odmget: Cannot open object class attribute=unique_id <br /> Check path name and permissions. <div>&nbsp;</div> So I did it this way and it did work! <div>&nbsp;</div> odmget -q name=hdisk8 CuAt | grep -p unique_id <br /> CuAt: <br /> name = "hdisk8" <br /> attribute = "unique_id" <br /> value = "26112001738002776004D072810XIV03IBMfcp" <br /> type = "R" <br /> generic = "D" <br /> rep = "nl" <br /> nls_index = 79 <div>&nbsp;</div> Or, as you mentioned in the article, run "lsattr -El hdiskN -a unique_id" to show the unique_id value. <div>&nbsp;</div> BTW, I like reading your blog article! It's always teaching me a lot! Thank you very much, AnthonyEnglish!

4 AnthonyEnglish commented Permalink

Thanks for your comment, Nostrum. I had the syntax wrong for that odmget command. This should work: <div>&nbsp;</div> odmget -q"name=hdiskN and attribute=unique_id" CuAt <div>&nbsp;</div> (insert the correct hdisk number, e.g. hdisk10) <div>&nbsp;</div> and of course you can use the grep command with the -p option to capture the whole paragraph: <br /> odmget -q"name=hdisk10" CuAt | grep -ip unique_id

5 nostrum commented Permalink

Got it! I'll take a note of your odmget command mentioned in comment 4! Thank you, AnthonyEnglish! :-)