Date: 20-10-20  Time: 14:22 PM

Author Topic: CDROM device not detected by new lpar  (Read 30560 times)

0 Members and 1 Guest are viewing this topic.

Carl

  • Jr. Member
  • **
  • Posts: 7
  • Karma: +0/-0
CDROM device not detected by new lpar
« on: November 13, 2007, 09:17:29 AM »
I have created a new logical partition on the p590 of a customer and would like to install AIX on it. The p590 has a dvd-writer attached to it via a SCSI cable. Practically all lpars make use of it, including the virtual i/o servers. I am quite sure I have added this device as a desired physical i/o. I have put the first CD of the AIX package into the drive and started up the new lpar. I would like to boot from CD/DVD so as to be able to install AIX, but the lpar does not detect this device. Could anyone help me with this little inconvenience? Thanks in advance.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1267
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #1 on: November 13, 2007, 06:09:56 PM »
If you put it as desired it may be that it is in use by one of the other partitions. Desired means you get it ONLY if it is not in use elsewhere. Also, desired means that if it is not there, the partition may be activated anyway.

Required means the partition will not activate unless the device is available; however, it also means it cannot be passed to another partition via DLPAR actions.

Recommended: create a virtual scsi interface between a VIO server and the partition to support the dvd (assuming you are not using virtual scsi for regular production). I also recommend a seperate profile for setup or installation (then required, as an attribute, may be less dangerous).

If this is still unclear, tell me what I missed - and I'll add the extra info!

Carl

  • Jr. Member
  • **
  • Posts: 7
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #2 on: November 13, 2007, 06:54:19 PM »
Dear Michael

thank you for your reply.
I will just try to summarize what you said in my own words to try and find out whether I understand:
In the wonderful world of my p590 there exists a physical i/o device named "Storage Controller". I am quite sure this is the cdrom (CD/DVD). It is currently "owned" by virtual i/o server number one as a desired object.
I removed it with rmdev -dlR pci4 from the virtual i/o server to try out my AIX install from CD/DVD, but it did not work. More specifically: no device was found. I made sure to put it back again via cfgmgr (and the magic worked).
One of the things you're suggesting is that I create a virtual i/o adapter that contains the cdrom on virtual i/o server number one and then make it available to my new server for a fresh install of AIX 5.3. Since the cdrom is a physical i/o device I haven't got the faintest idea how to do this (it certainly wasn't covered in the course you gave me at IBM).
Thanks in advance for your help.

Carl

  • Jr. Member
  • **
  • Posts: 7
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #3 on: November 14, 2007, 06:44:16 AM »
I did it!
I removed the cdrom from the virtual i/o server via rmdev -dl pci4 -R AND took it out of the machine via DLPAR. Now I started my new lpar and it recognized the cdrom as a device of which it can boot.
Thank you Michael for your help!

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1267
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #4 on: November 14, 2007, 01:00:52 PM »
Excellent - although I am challanged by your comment that we did not cover this in the class. Maybe I failed to stress the ability of VIOS to host the cd device.

To correct this 'problem':

At the command level, the basic command for creating a virtual target device is:
mkvdev. The command to remove a virtual target device is rmvdev.

Valid storage devices are logical volumes, physical volumes, and optical devices (i.e. cd0 aka dvd device).

You need to know whcih vhost adapter a client is goinf to use, so I shall just say X and Y for moving a virtual device between two (logical) partitions.

As padmin (not root),

$ mkvdev -vdev /dev/cd0 -vadapter vhostX [-dev vtcd0]

The above assigns the cd0 to the partitionX which will see it as /dev/cd0 (assuming no other cd devices have been defined in the ODM).

Verify with:

$ lsmap -vadapter vhostX

$ rmvdev -vtd vtcd0  # maybe a force argument will be needed as well, if the device is allocated to an active partition.

$ mkvdev -vdev /dev/cd0 -vadapter vhostY [-dev vtcd0]

Try this out - if I am missing any steps, let me know! Thanks for your continuing feedback.

Carl

  • Jr. Member
  • **
  • Posts: 7
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #5 on: December 12, 2007, 08:07:22 AM »
Okay, thanks again for your feedback.
Let us just raise the bar a bit and I will present you a new challenge.
I do not have DLPAR now! (no communication between vios's and HMC, but IBM is busy with it (it is a darn mystery))
Yesterday I created a whole bunch (four) new lpars and decided to install the O.S. on them today. For this I need the cdrom device owned by one of the vios's.
You mentioned something about creating a virtual cd-device, but I failed to see the connection between the vios and the lpar I would like to use it on (X and/or Y).
Please do elaborate on the command you used below:
$ mkvdev -vdev /dev/cd0 -vadapter vhostX (how to make the vhostX known to the target lpar?)

Thanks in advance!

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1267
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #6 on: December 12, 2007, 12:37:07 PM »
No communication between HMC and VIOS? What level of HMC and VIOS are you running? What does lparstat say? On VIOS and root, run the following command. (Note, you will get one error as the first line is not a manageable object, but a header.)

# for i in `lsrsrc`
> do
> lsrsrc $i
> done


This will tell you all the partition knows, and all the VIOS knows. In particular, you are wanting to be sure that the classes IBM.Host, IBM.ManagedNode, and IBM.ManagementServer. At least, ina an IVM environment (no HMC) those are the ones I am most interested while on the VIOS.

On an LPAR (which a VIO partition is when a HMC is used to configure the system) you need to make sure that the IBM.ManagementServer is filled in with addresses that are not blocked by a firewall - as these generally go over a so-called public network (by definition, the closed/private network is for HMC/ServiceProcessor exclusively - and not for DLPAR control.)

For example: x200 is my IVM (vios, but acting as an HMC would) and x202 is a partition:
Resource Persistent Attributes for "IBM.ManagementServer"
resource 1:
        Name             = "192.168.129.200"
        Hostname         = "192.168.129.200"
        ManagerType      = "HMC"
        LocalHostname    = "192.168.129.202"
        ClusterTM        = "9078-160"
        ClusterSNum      = ""
        ActivePeerDomain = ""
        NodeNameList     = {"x202"}


Note that even here, the LPAR x202, is saying that X200 is an HMC, even though it is a LPAR.

regarding itself: x200 says:
Resource Persistent Attributes for "IBM.ManagementServer"
resource 1:
        Name             = "192.168.129.200"
        Hostname         = "192.168.129.200"
        ManagerType      = "HMC"
        LocalHostname    = "192.168.129.200"
        ClusterTM        = "9078-160"
        ClusterSNum      = ""
        ActivePeerDomain = ""
        NodeNameList     = {"x200"}


LocalHostname == Hostname

So, this is the bit for DLPAR communication debugging.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1267
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #7 on: December 12, 2007, 12:58:44 PM »
1) the VIO partition needs to "own" the /dev/cd0
2) You need to know if a virtual CD (Optical Device) has been defined
3) You need the Location Code of the virtual device
4) Locate the slot to identify the vhost adapter it is attached to
5) If this is not want you want, you will need to remove the optical device using rmvdev, and remake it on the correct vhost adapter.

$ lsdev | grep cd0
cd0             Available  IDE DVD-ROM Drive
$ lsdev -virtual | grep Optical
vtopt0          Available  Virtual Target Device - Optical Media
$ lsdev -dev vtopt0 -vpd
  vtopt0           U9110.51A.0639B9D-V1-C11-L2  Virtual Target Device - Optical Media
$ lsdev -slots
# Slot                       Description       Device(s)
U788C.001.AAA4406-P1-C14-C1  Logical I/O Slot  pci7 fcs0
U788C.001.AAA4406-P1-T1      Logical I/O Slot  pci3 ent0 ent1
U788C.001.AAA4406-P1-T3      Logical I/O Slot  pci4 usbhc0 usbhc1
U788C.001.AAA4406-P1-T10     Logical I/O Slot  pci6 sisscsia0
U788C.001.AAA4406-P1-T12     Logical I/O Slot  pci5 ide0
U9110.51A.0639B9D-V1-C2      Virtual I/O Slot  ibmvmc0
U9110.51A.0639B9D-V1-C3      Virtual I/O Slot  ent2
U9110.51A.0639B9D-V1-C4      Virtual I/O Slot  ent3
U9110.51A.0639B9D-V1-C5      Virtual I/O Slot  ent4
U9110.51A.0639B9D-V1-C6      Virtual I/O Slot  ent5
U9110.51A.0639B9D-V1-C10     Virtual I/O Slot  vts0
U9110.51A.0639B9D-V1-C11     Virtual I/O Slot  vhost0
U9110.51A.0639B9D-V1-C12     Virtual I/O Slot  vts1
U9110.51A.0639B9D-V1-C13     Virtual I/O Slot  vhost1

$ lsmap -vadapter vhost0
SVSA            Physloc                                      Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0          U9110.51A.0639B9D-V1-C11                     0x00000002

VTD                   vtopt0
Status                Available
LUN                   0x8200000000000000
Backing device        cd0
Physloc               U788C.001.AAA4406-P1-D5

VTD                   vtscsi0
Status                Available
LUN                   0x8100000000000000
Backing device        lp2vd1
Physloc

VTD                   vtscsi1
Status                Available
LUN                   0x8300000000000000
Backing device        lp2cd2
Physloc

$ $ rmvdev -vtd vtopt0
vtopt0 deleted
$ mkvdev -vdev cd0 -vadapter vhost1
vtopt0 Available
$ lsdev -dev vtopt0 -vpd
  vtopt0           U9110.51A.0639B9D-V1-C13-L2  Virtual Target Device - Optical
Media
$ lsmap -vadapter vhost1
SVSA            Physloc                                      Client Partition ID
--------------- -------------------------------------------- ------------------
vhost1          U9110.51A.0639B9D-V1-C13                     0x00000003

VTD                   vtopt0
Status                Available
LUN                   0x8200000000000000
Backing device        cd0
Physloc               U788C.001.AAA4406-P1-D5

VTD                   vtscsi2
Status                Available
LUN                   0x8100000000000000
Backing device        lp3vd1
Physloc

$

These commands only change the mapping. The partitions still need to run cfgmgr to move the device to Available. And I doubt if the partition that has the virtual cd0 will enjoy having it taken in this way (at least VIOS and IVM can "steal/force" the movement of the optical device. I would have to test on a VIO running together with a HMC to know for sure.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1267
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #8 on: December 12, 2007, 01:54:36 PM »
A little more checking - and the real experts recommend verifying the IBM.ManagedNode resource on the HMC (or VIO acting as HMC aka IVM - Integrated Virtualization Manager)

Note: getting some nice keywords in here!

Carl

  • Jr. Member
  • **
  • Posts: 7
  • Karma: +0/-0
Re: CDROM device not detected by new lpar
« Reply #9 on: January 29, 2008, 10:09:47 AM »
Dear Michael

thank you for your help and advice, but it was to no avail. In the end and after much trouble shooting with IBM engineers, we found out that the problem was two routes in the HMC network configuration. Those two routes apparently caused a problem with the communication between the HMC and the lpars. We removed the routes and all worked smooth as possible.
Thanks again for your feedback, I learned much of it. My appologies for replying so late.

Greetings
Carl