Topic
  • 26 replies
  • Latest Post - ‏2013-03-22T14:16:47Z by JayFurmanek
dtoolman.dan
dtoolman.dan
20 Posts

Pinned topic Got Toolkit to Boot ... Now What ... ?

‏2013-03-05T18:03:14Z |
Dual VIO presenting a single dual-pathed vscsi 100GB boot volume to LPAR 
PowerLinux Toolkit 5.3 
Attempting to install RHEL 6.3 via the Toolkit ... RHEL ISO presented via nfs off another Linux host
Toolkit ISO presented to the lpar via a VM Library and Virtual Optical Device on 1 of the 2 VIO
 
Toolkit boots ... gets into Wizard mode, pulled up on browser to continue the config ... 100GB volume is seen as mpatha (sda, sdb) ... all good so far
Work through the wizard and configure ... to the point where it will install Linux ... click Next
 
[snip] 
Distro installation will begin on next boot from hard disk. Rebooting in 5 seconds...
 
lpar Reboots then cannot find any boot device to boot from to continue the install or RHEL from ... sorry the the verbosity ... but Now What?
Manually working SMS and it still cannot discover any bootable device ... ? 
 
Thanks! 
Dan 

Updated on 2013-03-22T14:16:47Z at 2013-03-22T14:16:47Z by JayFurmanek
  • lucio.correia
    lucio.correia
    19 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-05T19:42:33Z  
     Hi Dan,
     
    Thanks for reporting this issue. 
     
    The "cannot find any boot device" error may occur when there is a USB key attached to the system on RHEL installations. The workaround would be manually working SMS like you did, or removing the USB key. 
     
    We are going to reproduce your environment in order to investigate this issue.
     
    Thanks
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-07T14:41:56Z  
     Hi Dan,
     
    Thanks for reporting this issue. 
     
    The "cannot find any boot device" error may occur when there is a USB key attached to the system on RHEL installations. The workaround would be manually working SMS like you did, or removing the USB key. 
     
    We are going to reproduce your environment in order to investigate this issue.
     
    Thanks
     For further clarity ... there is no USB device plugged into the VIO or otherwise.
     I intent-fully  avoided this so I didn't need to keep walking to/from the lab.
     
    Yes ... please advise, Thanks!
    Dan
      
     
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-08T04:56:27Z  
    SMS may not show the vSCSI device since it has not been installed to and made bootable.
     
    IBMIT does support multipath installs, but it is a new feature.
    As I posted on your other thread (didn't see this one till now!) I'd recommend just installing with the RHEL media since you are having trouble with the toolkit.  Anaconda, the installer that RedHat uses, supports installing to multipath'd storage by default. Be sure to pick to install to a 'specialized' device when you get to picking an install device. You need the graphical install, which can be activated with the "vnc" boot parameter.
    Updated on 2013-03-08T04:56:27Z at 2013-03-08T04:56:27Z by JayFurmanek
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-08T04:58:16Z  
    SMS may not show the vSCSI device since it has not been installed to and made bootable.
     
    IBMIT does support multipath installs, but it is a new feature.
    As I posted on your other thread (didn't see this one till now!) I'd recommend just installing with the RHEL media since you are having trouble with the toolkit.  Anaconda, the installer that RedHat uses, supports installing to multipath'd storage by default. Be sure to pick to install to a 'specialized' device when you get to picking an install device. You need the graphical install, which can be activated with the "vnc" boot parameter.
     What is IBMIT ... ?
     And I still cannot get RHEL to boot on the LPAR ... when the ISO is presented via the VirtOpt. device ...
     Thanks!
        
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-08T04:59:04Z  
    SMS may not show the vSCSI device since it has not been installed to and made bootable.
     
    IBMIT does support multipath installs, but it is a new feature.
    As I posted on your other thread (didn't see this one till now!) I'd recommend just installing with the RHEL media since you are having trouble with the toolkit.  Anaconda, the installer that RedHat uses, supports installing to multipath'd storage by default. Be sure to pick to install to a 'specialized' device when you get to picking an install device. You need the graphical install, which can be activated with the "vnc" boot parameter.
     Whats the magic sauce I'm missing in this ... I can't imagine its that hard ... 
     
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-08T05:52:37Z  
     What is IBMIT ... ?
     And I still cannot get RHEL to boot on the LPAR ... when the ISO is presented via the VirtOpt. device ...
     Thanks!
        
     IBMIT= IBM Installation Toolkit
     
    For a vOpt device, the mapping should look like:
     
     $ lsmap -all
    SVSA            Physloc                                      Client Partition ID
    --------------- -------------------------------------------- ------------------
    vhost0          U8202.E4B.102702P-V1-C11                     0x00000002

    VTD                   vtopt0
    Status                Available
    LUN                   0x8200000000000000
    Backing device        /var/vio/VMLibrary/SLES11SP2.iso
    Physloc                
    Mirrored              N/A

    VTD                   vtscsi1
    Status                Available
    LUN                   0x8100000000000000
    Backing device        vDisk1
    Physloc                
    Mirrored              N/A
     
    Are you using the HMC GUI to load the ISO, or the loadopt command?
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-08T06:09:43Z  
     IBMIT= IBM Installation Toolkit
     
    For a vOpt device, the mapping should look like:
     
     $ lsmap -all
    SVSA            Physloc                                      Client Partition ID
    --------------- -------------------------------------------- ------------------
    vhost0          U8202.E4B.102702P-V1-C11                     0x00000002

    VTD                   vtopt0
    Status                Available
    LUN                   0x8200000000000000
    Backing device        /var/vio/VMLibrary/SLES11SP2.iso
    Physloc                
    Mirrored              N/A

    VTD                   vtscsi1
    Status                Available
    LUN                   0x8100000000000000
    Backing device        vDisk1
    Physloc                
    Mirrored              N/A
     
    Are you using the HMC GUI to load the ISO, or the loadopt command?
     loadopt on the VIO ... 
     but seeing your layout sparks a few ideas ...
     I have 1 vhost device presenting/mapping the ISO ... but another vhost presenting the target installation boot device ... 
     
     I'm going to merge them into 1 and hopefully get some luck there ... thanks for the idea, I'll post back when I get to try this
     
     Dan
         
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-08T14:32:35Z  
     loadopt on the VIO ... 
     but seeing your layout sparks a few ideas ...
     I have 1 vhost device presenting/mapping the ISO ... but another vhost presenting the target installation boot device ... 
     
     I'm going to merge them into 1 and hopefully get some luck there ... thanks for the idea, I'll post back when I get to try this
     
     Dan
         
    btw, it's a good idea to use the -f on the loadopt command.
  • willschm
    willschm
    47 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-13T14:07:06Z  
     Whats the magic sauce I'm missing in this ... I can't imagine its that hard ... 
     
     > lpar Reboots then cannot find any boot device to boot from to continue the install or RHEL from
     
    If the system cannot find any device to boot from, it may be a variation of the real-base/load-base issue.  We have seen in the past where SMS/OF will be unable to properly read from disks (or even detect them) if the real-base / load-base settings are 'just right'.    I'd recommend trying a nvram reset and see if the boot devices show up afterwards.
     
    Drop to the OFW prompt, and do:
    dev /nvram
    wipe-nvram
     
    The lpar will restart with cleared settings, and you will need to re-enter any net-boot / boot order settings in SMS . 

  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T18:51:41Z  
    • willschm
    • ‏2013-03-13T14:07:06Z
     > lpar Reboots then cannot find any boot device to boot from to continue the install or RHEL from
     
    If the system cannot find any device to boot from, it may be a variation of the real-base/load-base issue.  We have seen in the past where SMS/OF will be unable to properly read from disks (or even detect them) if the real-base / load-base settings are 'just right'.    I'd recommend trying a nvram reset and see if the boot devices show up afterwards.
     
    Drop to the OFW prompt, and do:
    dev /nvram
    wipe-nvram
     
    The lpar will restart with cleared settings, and you will need to re-enter any net-boot / boot order settings in SMS . 

     ... still stuck ... and thank you everyone for the thoughts & suggestions so far ... per the suggestions above
     
    i'm back down to 1 vhost per lpar as below
     
    $ lsmap -all
    SVSA            Physloc                                      Client Partition ID
    --------------- -------------------------------------------- ------------------
    vhost0          U8231.E2B.068426P-V2-C22                     0x00000017

    VTD                   dellstud3_cd0 ... this is single vopt device attached via 1 of the 2 VIO
    Status                Available
    LUN                   0x8300000000000000
    Backing device        /var/vio/VMLibrary/IBM_Installation_Toolkit_53.iso
    Physloc
    Mirrored              N/A

    VTD                   hacmp-boot ... ignote the VTD label, this is a 100GB volume presented to the lpar via dual VIO
    Status                Available
    LUN                   0x8100000000000000
    Backing device        hdisk1
    Physloc               U78AB.001.WZSG9ZN-P1-C3-T2-W5000D3100000670B-L2000000000000
    Mirrored              false    
     
    boot into IBMIT ... setup, and configure & boot & reboot ... see this mesg
     
    [snip] 
    Distro installation will begin on next boot from hard disk. Rebooting in 5 seconds...
     
    and back to SMS ... and still cannot find boot device ... i also tried the "dev nvram; wipe-nvram" sequence ... and after doing so, tried a search for boot devices in SMS ... and don't see any 
     
     PowerPC Firmware
     Version AL730_035
     SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.
    -------------------------------------------------------------------------------
     Select Device
     Device  Current  Device
     Number  Position  Name
     1.        2      Interpartition Logical LAN
            ( loc=U8231.E2B.068426P-V23-C50-T1 )
     2.        -      Interpartition Logical LAN
            ( loc=U8231.E2B.068426P-V23-C51-T1 )
     3.        1      SCSI CD-ROM
            ( loc=U8231.E2B.068426P-V23-C2-T1-L8300000000000000 ) 
     
    Help! 
    Dan 
     
      
     
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T19:00:57Z  
     ... still stuck ... and thank you everyone for the thoughts & suggestions so far ... per the suggestions above
     
    i'm back down to 1 vhost per lpar as below
     
    $ lsmap -all
    SVSA            Physloc                                      Client Partition ID
    --------------- -------------------------------------------- ------------------
    vhost0          U8231.E2B.068426P-V2-C22                     0x00000017

    VTD                   dellstud3_cd0 ... this is single vopt device attached via 1 of the 2 VIO
    Status                Available
    LUN                   0x8300000000000000
    Backing device        /var/vio/VMLibrary/IBM_Installation_Toolkit_53.iso
    Physloc
    Mirrored              N/A

    VTD                   hacmp-boot ... ignote the VTD label, this is a 100GB volume presented to the lpar via dual VIO
    Status                Available
    LUN                   0x8100000000000000
    Backing device        hdisk1
    Physloc               U78AB.001.WZSG9ZN-P1-C3-T2-W5000D3100000670B-L2000000000000
    Mirrored              false    
     
    boot into IBMIT ... setup, and configure & boot & reboot ... see this mesg
     
    [snip] 
    Distro installation will begin on next boot from hard disk. Rebooting in 5 seconds...
     
    and back to SMS ... and still cannot find boot device ... i also tried the "dev nvram; wipe-nvram" sequence ... and after doing so, tried a search for boot devices in SMS ... and don't see any 
     
     PowerPC Firmware
     Version AL730_035
     SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.
    -------------------------------------------------------------------------------
     Select Device
     Device  Current  Device
     Number  Position  Name
     1.        2      Interpartition Logical LAN
            ( loc=U8231.E2B.068426P-V23-C50-T1 )
     2.        -      Interpartition Logical LAN
            ( loc=U8231.E2B.068426P-V23-C51-T1 )
     3.        1      SCSI CD-ROM
            ( loc=U8231.E2B.068426P-V23-C2-T1-L8300000000000000 ) 
     
    Help! 
    Dan 
     
      
     
     PS. in the Linux setup, configure pages ... it see a boot device ... mpatha (sda, sdb) ...
     
    Hmmm 
    Dan 
     
  • willschm
    willschm
    47 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T19:41:27Z  
     ... still stuck ... and thank you everyone for the thoughts & suggestions so far ... per the suggestions above
     
    i'm back down to 1 vhost per lpar as below
     
    $ lsmap -all
    SVSA            Physloc                                      Client Partition ID
    --------------- -------------------------------------------- ------------------
    vhost0          U8231.E2B.068426P-V2-C22                     0x00000017

    VTD                   dellstud3_cd0 ... this is single vopt device attached via 1 of the 2 VIO
    Status                Available
    LUN                   0x8300000000000000
    Backing device        /var/vio/VMLibrary/IBM_Installation_Toolkit_53.iso
    Physloc
    Mirrored              N/A

    VTD                   hacmp-boot ... ignote the VTD label, this is a 100GB volume presented to the lpar via dual VIO
    Status                Available
    LUN                   0x8100000000000000
    Backing device        hdisk1
    Physloc               U78AB.001.WZSG9ZN-P1-C3-T2-W5000D3100000670B-L2000000000000
    Mirrored              false    
     
    boot into IBMIT ... setup, and configure & boot & reboot ... see this mesg
     
    [snip] 
    Distro installation will begin on next boot from hard disk. Rebooting in 5 seconds...
     
    and back to SMS ... and still cannot find boot device ... i also tried the "dev nvram; wipe-nvram" sequence ... and after doing so, tried a search for boot devices in SMS ... and don't see any 
     
     PowerPC Firmware
     Version AL730_035
     SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.
    -------------------------------------------------------------------------------
     Select Device
     Device  Current  Device
     Number  Position  Name
     1.        2      Interpartition Logical LAN
            ( loc=U8231.E2B.068426P-V23-C50-T1 )
     2.        -      Interpartition Logical LAN
            ( loc=U8231.E2B.068426P-V23-C51-T1 )
     3.        1      SCSI CD-ROM
            ( loc=U8231.E2B.068426P-V23-C2-T1-L8300000000000000 ) 
     
    Help! 
    Dan 
     
      
     

    [snip]   Distro installation will begin on next boot from hard disk. Rebooting in 5 seconds...
     
     PS. in the Linux setup, configure pages ... it see a boot device ... mpatha (sda, sdb) ...
     
    Interesting..     so possibly something is going wrong in how the IT is marking (trying to mark) one of those devices as bootable?
    (IBMIT guys?  back over to you.. ;-)   ) 
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T20:34:37Z  
    • willschm
    • ‏2013-03-14T19:41:27Z

    [snip]   Distro installation will begin on next boot from hard disk. Rebooting in 5 seconds...
     
     PS. in the Linux setup, configure pages ... it see a boot device ... mpatha (sda, sdb) ...
     
    Interesting..     so possibly something is going wrong in how the IT is marking (trying to mark) one of those devices as bootable?
    (IBMIT guys?  back over to you.. ;-)   ) 
     Am I doing anything different than anyone else ... whom might have gotten this to work?
     And I'm sure this cannot be that hard.
     Is this a VIO or HMC firmware issue?
     Thanks!
       
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T20:59:31Z  
     Am I doing anything different than anyone else ... whom might have gotten this to work?
     And I'm sure this cannot be that hard.
     Is this a VIO or HMC firmware issue?
     Thanks!
       
    I'm not an IBMIT guy, but the way IBMIT works, is it builds a kickstart file, then reboots and uses the RHEL installation media to do the actual install.
    You should mount *both* IBMIT and the RHEL disc on two separate vOpt devices.
    Note the LUN number from the lsmap -all output. That is how to know which is which when booting from SMS (SMS won't show the actual ISO name loaded).
     
    In your other thread, you mentioned that you couldn't boot directly into the RHEL media (No software found). Is that still the case? If so, then the IBMIT install won't find it either.
    Perhaps that is your main problem.
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T21:03:02Z  
    I'm not an IBMIT guy, but the way IBMIT works, is it builds a kickstart file, then reboots and uses the RHEL installation media to do the actual install.
    You should mount *both* IBMIT and the RHEL disc on two separate vOpt devices.
    Note the LUN number from the lsmap -all output. That is how to know which is which when booting from SMS (SMS won't show the actual ISO name loaded).
     
    In your other thread, you mentioned that you couldn't boot directly into the RHEL media (No software found). Is that still the case? If so, then the IBMIT install won't find it either.
    Perhaps that is your main problem.
     Try to get your lsmap output to look like:
     
     
    $ lsmap -all
    SVSA            Physloc                                      Client Partition ID
    --------------- -------------------------------------------- ------------------
    vhost0          U8231.E2B.068426P-V2-C22                     0x00000017

    VTD                   dellstud3_cd0
    Status                Available
    LUN                   0x8300000000000000
    Backing device        /var/vio/VMLibrary/IBM_Installation_Toolkit_53.iso
    Physloc
    Mirrored              N/A
     
    VTD                   dellstud3_cd1
    Status                Available
    LUN                   0x8200000000000000
    Backing device        /var/vio/VMLibrary/RHEL63.iso
    Physloc
    Mirrored              N/A
     
    VTD                   hacmp-boot
    Status                Available
    LUN                   0x8100000000000000
    Backing device        hdisk1
    Physloc               U78AB.001.WZSG9ZN-P1-C3-T2-W5000D3100000670B-L2000000000000
    Mirrored              false   
    Updated on 2013-03-14T21:03:02Z at 2013-03-14T21:03:02Z by JayFurmanek
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T21:06:52Z  
    I'm not an IBMIT guy, but the way IBMIT works, is it builds a kickstart file, then reboots and uses the RHEL installation media to do the actual install.
    You should mount *both* IBMIT and the RHEL disc on two separate vOpt devices.
    Note the LUN number from the lsmap -all output. That is how to know which is which when booting from SMS (SMS won't show the actual ISO name loaded).
     
    In your other thread, you mentioned that you couldn't boot directly into the RHEL media (No software found). Is that still the case? If so, then the IBMIT install won't find it either.
    Perhaps that is your main problem.
     That was my initial approach with 2 vOpt devices ... but then in the IBMIT config ... it got very confused which vOpt device had the RHEL iso and kept defaulting to the IBMIT vOpt (thus not finding the RHEL iso).
     Currently, RHEL media is fed via a nfs repo of another Linux machine
     ... then again ... this was fed via 2 different vhosts as well) ... i'll try this approach and advise back ...
     
     regardless, it is finding the RHEL iso ... and inside of the config ... it see the boot target install device ... but after the 1st reboot ... it cannot find it thereafter ... or maybe SMS cannot find it over NFS?
     yes, trying to boot RHEL iso via 1 vhost 1 vopt ... still gives me No Software Found  
     
     where does it write (or attempt) to write the /tmp/kickstart file? 
     
     Dan 
     
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-14T21:23:19Z  
     That was my initial approach with 2 vOpt devices ... but then in the IBMIT config ... it got very confused which vOpt device had the RHEL iso and kept defaulting to the IBMIT vOpt (thus not finding the RHEL iso).
     Currently, RHEL media is fed via a nfs repo of another Linux machine
     ... then again ... this was fed via 2 different vhosts as well) ... i'll try this approach and advise back ...
     
     regardless, it is finding the RHEL iso ... and inside of the config ... it see the boot target install device ... but after the 1st reboot ... it cannot find it thereafter ... or maybe SMS cannot find it over NFS?
     yes, trying to boot RHEL iso via 1 vhost 1 vopt ... still gives me No Software Found  
     
     where does it write (or attempt) to write the /tmp/kickstart file? 
     
     Dan 
     
     hmm...lots of different info there.  The common theme, though, is not being able to boot from the RHEL media, which is required for any install method.
     
    SMS cannot do NFS, there are no system services enabled at that point. It only knows about devices (real or virtual) in the device tree. The RHEL ISO needs to be added to the VMLibrary just as the IBMIT ISO was, and loaded into a vOpt device in the same way in order for SMS to boot from it.
     
    The IBMIT can install from an NFS RHEL target, but it just pulls the install resources from there. The lpar still needs a method of booting. The RHEL install disc provides the boot resources (in addition to the installation resources if needed).
     
    Make sense?
    Updated on 2013-03-14T21:23:19Z at 2013-03-14T21:23:19Z by JayFurmanek
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-15T13:52:34Z  
     hmm...lots of different info there.  The common theme, though, is not being able to boot from the RHEL media, which is required for any install method.
     
    SMS cannot do NFS, there are no system services enabled at that point. It only knows about devices (real or virtual) in the device tree. The RHEL ISO needs to be added to the VMLibrary just as the IBMIT ISO was, and loaded into a vOpt device in the same way in order for SMS to boot from it.
     
    The IBMIT can install from an NFS RHEL target, but it just pulls the install resources from there. The lpar still needs a method of booting. The RHEL install disc provides the boot resources (in addition to the installation resources if needed).
     
    Make sense?
    Crystal ... I hope that is it ... more to come. 
     
    Thanks! 
    Dan 
     
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-15T14:32:52Z  
    Crystal ... I hope that is it ... more to come. 
     
    Thanks! 
    Dan 
     
     So before I click Next to install RHEL ... after I have already setup 2 vOpt like above ... shouldn't I unloadopt the IBMIT iso before I proceeed?
     Dan
      
  • lucio.correia
    lucio.correia
    19 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-15T15:12:39Z  
     So before I click Next to install RHEL ... after I have already setup 2 vOpt like above ... shouldn't I unloadopt the IBMIT iso before I proceeed?
     Dan
      
    It's not necessary to unload IBMIT. It will be necessary after Linux installation in order to install IBM packages.
     
    Even if you have only one vOpt, IBMIT would ask you to change to Linux media before installation, and also would ask IBMIT media again after installation to install IBM packages. Thus having 2 vOpts is not mandatory, we do support only one vOpt or physical drive. 
  • lucio.correia
    lucio.correia
    19 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-15T15:27:50Z  
    I'm not an IBMIT guy, but the way IBMIT works, is it builds a kickstart file, then reboots and uses the RHEL installation media to do the actual install.
    You should mount *both* IBMIT and the RHEL disc on two separate vOpt devices.
    Note the LUN number from the lsmap -all output. That is how to know which is which when booting from SMS (SMS won't show the actual ISO name loaded).
     
    In your other thread, you mentioned that you couldn't boot directly into the RHEL media (No software found). Is that still the case? If so, then the IBMIT install won't find it either.
    Perhaps that is your main problem.
     Regarding NFS case, some IBMIT explanation is needed here.
     
    IBMIT generates a kickstart, but the installation is not triggered from Red Hat media. IBMIT configures a special partition from which the system boots and triggers Linux installation using the Red Hat repository informed, either DVD, HTTP, FTP or NFS. Thus the boot for Linux installation is always triggered from the disk.
     
    What kind of partitioning is being used?
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-15T15:41:03Z  
     So before I click Next to install RHEL ... after I have already setup 2 vOpt like above ... shouldn't I unloadopt the IBMIT iso before I proceeed?
     Dan
      
     Keep both ISOs loaded.
    It'll know which vOpt drive to go to, to get what it needs.
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-18T21:06:16Z  
     Regarding NFS case, some IBMIT explanation is needed here.
     
    IBMIT generates a kickstart, but the installation is not triggered from Red Hat media. IBMIT configures a special partition from which the system boots and triggers Linux installation using the Red Hat repository informed, either DVD, HTTP, FTP or NFS. Thus the boot for Linux installation is always triggered from the disk.
     
    What kind of partitioning is being used?
     Is this why I'm choking on this ...
     $ lsvopt
    VTD             Media                                   Size(mb)
    dellstud3_cd0   IBM_Installation_Toolkit_53.iso             1006
    dellstud3_cd1   rhel-server-6.3-x86_64-dvd.iso              3509
     
    Thats a x86_64 RHEL iso up there ... is there a different ISO for POWER h/w? 
     
     Dan 
     
  • lucio.correia
    lucio.correia
    19 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-18T21:15:32Z  
     Is this why I'm choking on this ...
     $ lsvopt
    VTD             Media                                   Size(mb)
    dellstud3_cd0   IBM_Installation_Toolkit_53.iso             1006
    dellstud3_cd1   rhel-server-6.3-x86_64-dvd.iso              3509
     
    Thats a x86_64 RHEL iso up there ... is there a different ISO for POWER h/w? 
     
     Dan 
     
     Yes. You need to download the ppc64 version of DVD.
  • dtoolman.dan
    dtoolman.dan
    20 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-22T13:34:39Z  
     Yes. You need to download the ppc64 version of DVD.
     Just wanted to post back and say Thanks! to all whom replied ...
     Sometimes the most obvious is unseen ... with a ppc/based ISO, this all worked as intended in a 2 vOpt + 1 hdisk + 1 vhost setup and I did get my lpar to RHEL ppc 6.3.
     
     Thanks again!
     Dan
  • JayFurmanek
    JayFurmanek
    105 Posts

    Re: Got Toolkit to Boot ... Now What ... ?

    ‏2013-03-22T14:16:47Z  
     Just wanted to post back and say Thanks! to all whom replied ...
     Sometimes the most obvious is unseen ... with a ppc/based ISO, this all worked as intended in a 2 vOpt + 1 hdisk + 1 vhost setup and I did get my lpar to RHEL ppc 6.3.
     
     Thanks again!
     Dan
    Good to hear!