Topic
  • 18 replies
  • Latest Post - ‏2015-01-19T15:41:54Z by JayFurmanek
asingh1583
asingh1583
22 Posts

Pinned topic How to use kickstart file with /etc/bootptab for automated installation of Plinux

‏2013-03-14T04:48:15Z |
 Hi All,
 
I am able to automate the creation of lpar, assigning disk,assigning network and start installation with /etc/bootptab entry, but there i need to install manually, now the next option is to use the kickstart file @open firmware prompt.
The same i need to automate, means i shouldn't run this command on open firmware prompt.

0 > boot network:<serverIP>,,<clientIP>,<gatewayIP> linux ks=nfs:server.example.com/mydir/ks.cfg ksdevice=eth0 ip=<clientIP> netmask=<clientNetMask> gateway=<gatewayIP> noipv6

This command i need to run manually from OFP.
Is there any way to automate this command through script?
 
Any help would be highly appreciated.
 
Updated on 2013-03-28T09:57:46Z at 2013-03-28T09:57:46Z by asingh1583
  • anibal.carvalho
    anibal.carvalho
    40 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-14T13:06:19Z  
     You can use the ks=nfs:server.example.com/mydir/ks.cfg parameter directly on the lpar related yaboot.conf on your netboot server.
  • JayFurmanek
    JayFurmanek
    115 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-14T16:40:42Z  
     You can use the ks=nfs:server.example.com/mydir/ks.cfg parameter directly on the lpar related yaboot.conf on your netboot server.
     To clarify Anibal's statment, that line can go into the append line of the kernel entry in the yaboot.conf file.
     
    Something like:
     
     image=/ppc64/RHEL6.3/vmlinuz
            label=powerlinux
            initrd=/ppc64/RHEL6.3/initrd.img
            append="ks=nfs:server.example.com/mydir/ks.cfg ksdevice=eth0 ip=1.2.3.4 netmask=255.255.255.0 gateway=1.1.1.1"
            read-only

     
    To automate the IP assignment (so you dont have to enter the "boot network:<serverIP>,,<clientIP>,<gatewayIP>" part, you'll need to use DHCP as the BOOTP daemon instead of bootpd.   This has the benefit of working on Linux boot servers in addition to your AIX one. Helpful if you ever need to migrate or replicate the environment and don't have another AIX box.
     
    A DHCP entry may look like:
     
     host myhost.example.com {
            fixed-address 1.2.3.4
            hardware ethernet aa:bb:cc:dd:ee:ff
            filename "yaboot";
    }

    This entry tells a booting server with MAC addr aa:bb:cc:dd:ee:ff to take IP address 1.2.3.4, and then download the file yaboot via TFTP. This file is the actual yaboot binary. It will know to also grab the yaboot.conf file, which will contain info on where to download the install kernel and initrd, as well as your ks parameters to send to the install kernel.
     
    After all of this is set up, you should be able to just boot the server from the network from SMS, and it'll just go.
    Updated on 2013-03-14T16:40:42Z at 2013-03-14T16:40:42Z by JayFurmanek
  • JayFurmanek
    JayFurmanek
    115 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-14T16:45:32Z  
     You can use the ks=nfs:server.example.com/mydir/ks.cfg parameter directly on the lpar related yaboot.conf on your netboot server.
     Also, if you are using NIM, read the link below on how to incorporate DHCP into a NIM environment:
     
    http://pic.dhe.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.commadmn%2Fdoc%2Fcommadmndita%2Ftcpip_dhcp_nim.htm
  • asingh1583
    asingh1583
    22 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-15T05:12:29Z  
     To clarify Anibal's statment, that line can go into the append line of the kernel entry in the yaboot.conf file.
     
    Something like:
     
     image=/ppc64/RHEL6.3/vmlinuz
            label=powerlinux
            initrd=/ppc64/RHEL6.3/initrd.img
            append="ks=nfs:server.example.com/mydir/ks.cfg ksdevice=eth0 ip=1.2.3.4 netmask=255.255.255.0 gateway=1.1.1.1"
            read-only

     
    To automate the IP assignment (so you dont have to enter the "boot network:<serverIP>,,<clientIP>,<gatewayIP>" part, you'll need to use DHCP as the BOOTP daemon instead of bootpd.   This has the benefit of working on Linux boot servers in addition to your AIX one. Helpful if you ever need to migrate or replicate the environment and don't have another AIX box.
     
    A DHCP entry may look like:
     
     host myhost.example.com {
            fixed-address 1.2.3.4
            hardware ethernet aa:bb:cc:dd:ee:ff
            filename "yaboot";
    }

    This entry tells a booting server with MAC addr aa:bb:cc:dd:ee:ff to take IP address 1.2.3.4, and then download the file yaboot via TFTP. This file is the actual yaboot binary. It will know to also grab the yaboot.conf file, which will contain info on where to download the install kernel and initrd, as well as your ks parameters to send to the install kernel.
     
    After all of this is set up, you should be able to just boot the server from the network from SMS, and it'll just go.
     Hi Jay,
     
    Thanks for information, but still after appending ks file, the installation not going automatically.  Do we need to /etc/bootptab if using yaboot.conf?
    as i think its not reading the yaboot.conf file.
     
    Kindly give me some more details on this.
     
     
  • asingh1583
    asingh1583
    22 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-15T05:13:37Z  
     To clarify Anibal's statment, that line can go into the append line of the kernel entry in the yaboot.conf file.
     
    Something like:
     
     image=/ppc64/RHEL6.3/vmlinuz
            label=powerlinux
            initrd=/ppc64/RHEL6.3/initrd.img
            append="ks=nfs:server.example.com/mydir/ks.cfg ksdevice=eth0 ip=1.2.3.4 netmask=255.255.255.0 gateway=1.1.1.1"
            read-only

     
    To automate the IP assignment (so you dont have to enter the "boot network:<serverIP>,,<clientIP>,<gatewayIP>" part, you'll need to use DHCP as the BOOTP daemon instead of bootpd.   This has the benefit of working on Linux boot servers in addition to your AIX one. Helpful if you ever need to migrate or replicate the environment and don't have another AIX box.
     
    A DHCP entry may look like:
     
     host myhost.example.com {
            fixed-address 1.2.3.4
            hardware ethernet aa:bb:cc:dd:ee:ff
            filename "yaboot";
    }

    This entry tells a booting server with MAC addr aa:bb:cc:dd:ee:ff to take IP address 1.2.3.4, and then download the file yaboot via TFTP. This file is the actual yaboot binary. It will know to also grab the yaboot.conf file, which will contain info on where to download the install kernel and initrd, as well as your ks parameters to send to the install kernel.
     
    After all of this is set up, you should be able to just boot the server from the network from SMS, and it'll just go.
     Also in our environment we can't use DHCP.
  • JayFurmanek
    JayFurmanek
    115 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-15T15:55:52Z  
     Hi Jay,
     
    Thanks for information, but still after appending ks file, the installation not going automatically.  Do we need to /etc/bootptab if using yaboot.conf?
    as i think its not reading the yaboot.conf file.
     
    Kindly give me some more details on this.
     
     
     Does the system boot into the installer? If it does, then it likely found your yaboot.conf because otherwise it wouldn't have found the proper kernel and initrd for the installer.
     
    What does your bootpdtab entry look like?
     
    A couple things to note:
     - If the kickstart file is incomplete, or only answers a subset of the questions the installer asks, then the installer will have to default to interactive mode to retrieve that information.
     - If the installer can't access the specified kickstart file, it'll default to asking you where it is. Make sure the URL format is right.
     
    I may have had the format wrong in the above example..missing the colon after the system name (:)
    append="ks=nfs:server.example.com:/mydir/ks.cfg ksdevice=eth0 ip=1.2.3.4 netmask=255.255.255.0 gateway=1.1.1.1"
  • JayFurmanek
    JayFurmanek
    115 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-15T15:59:23Z  
     Also in our environment we can't use DHCP.
    You'll have to resort to a directed network boot then, which is a manual step.
    In SMS, this is called a Remote IPL (RIPL). You can use the SMS menus to set client and server IPs. Then allow it to boot from the network.
  • asingh1583
    asingh1583
    22 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-17T04:35:24Z  
     Does the system boot into the installer? If it does, then it likely found your yaboot.conf because otherwise it wouldn't have found the proper kernel and initrd for the installer.
     
    What does your bootpdtab entry look like?
     
    A couple things to note:
     - If the kickstart file is incomplete, or only answers a subset of the questions the installer asks, then the installer will have to default to interactive mode to retrieve that information.
     - If the installer can't access the specified kickstart file, it'll default to asking you where it is. Make sure the URL format is right.
     
    I may have had the format wrong in the above example..missing the colon after the system name (:)
    append="ks=nfs:server.example.com:/mydir/ks.cfg ksdevice=eth0 ip=1.2.3.4 netmask=255.255.255.0 gateway=1.1.1.1"
     Hi Jay,
     
    giving u the complete info. 
     
    bootptab entry 
     
    linux_test bf:/tmp/rhel/images/netboot/ppc.64img : client ip:serverip:gateway 
     and kickstart file kept under /tmp/rhel...
     and in yaboot
     linux_test
    label=linux 
    initrd.img=/tmp/rhel/ppc/ppc64/vmlinuz
    append=same as u explained 
    one more entry for ramdisk.gz 
    while booting its boot but donot take the kickstart file. 
    Also to mention thatwe r not using dhcp. 
    not aware whether its reading yaboot.conf file or not,how to boot with yaboot, means what settings i require to achieve this?
  • JayFurmanek
    JayFurmanek
    115 Posts

    Re: How to use kickstart file with /etc/bootptab for automated installation of Plinux

    ‏2013-03-18T15:30:47Z  
     Hi Jay,
     
    giving u the complete info. 
     
    bootptab entry 
     
    linux_test bf:/tmp/rhel/images/netboot/ppc.64img : client ip:serverip:gateway 
     and kickstart file kept under /tmp/rhel...
     and in yaboot
     linux_test
    label=linux 
    initrd.img=/tmp/rhel/ppc/ppc64/vmlinuz
    append=same as u explained 
    one more entry for ramdisk.gz 
    while booting its boot but donot take the kickstart file. 
    Also to mention thatwe r not using dhcp. 
    not aware whether its reading yaboot.conf file or not,how to boot with yaboot, means what settings i require to achieve this?
    So, for RHEL6, the ppc64.img file to too big for the firmware to pull over by itself (this is documented in the RHEL release notes). Instead, you must set your bootfile to the actual yaboot binary (the file called "yaboot" found at /ppc/chrp/yaboot on the RHEL media).
     
    Once yaboot is retrieved and started, it will automatically look in <TFTP_dir> and <TFTP_dir>/etc for the yaboot.conf file and retrieve it.
     
    From there, as long as it gets the correct kernel entry and the formats are all correct, it should work ok.