test

N1 Provisioning Server 3.1, Blades Edition, System Administration Guide

Customizing the JumpStart Boot and Configuration Server

This section describes how to set up and customize the JumpStart boot and configuration server on SPARC and x86 architectures. The JumpStart environment ensures that all the required software is installed on the resource pool server. This section describes customization of the JumpStart boot and configuration server on SPARC and x86 architectures.

If you have specific JumpStart customizations you must merge the scripts provided for N1 Provisioning Server with your customizations. The following example procedures for customizing the JumpStart boot and configuration server for SPARC and x 86 architectures set up a JumpStart environment that uses DHCP.

ProcedureTo Customize the Boot and Configuration Server for the SPARC Architecture

Steps

  1. Create the JumpStart directory on image server.

    Example:


    mkdir -p /images/jumpstart-sparc

  2. Verify that the path to the JumpStart directory is shared appropriately by typing:


    share | grep /images/jumpstart-sparc

    If the path is displayed and anon=0 is displayed in the options, proceed to the next step. If the path is not displayed or you do not have anon=0 in the options, continue with this step.

    1. Make the JumpStart directory NFS shared by adding the following entry to the /etc/dfs/dfstab file. 


      share -F nfs -o anon=0,rw=@10.42.42.0/24 -d "jumpstart server directory sparc" 
/images/jumpstart-sparc

    2. Make sure the JumpStart server's directory path is correctly shared.


      ps -ef | grep nfsd

      If the nfsd daemon is not running, start it by typing /etc/init.d/nfs.server start.

      If the nfsd daemon is running, share the JumpStart server by typing shareall.

  3. Use the following two scripts to customize the JumpStart begin and postinstallation for N1 Provisioning Server and copy them to the JumpStart directory:


    cp /tftpboot/terraspring/jumpstart/profiles/begin_js.sh 
/images/jumpstart-sparc
cp /tftpboot/terraspring/jumpstart/profiles/postinstall.sh /images/jumpstart-sparc

    See Customizing the Resource Pool Server Manually if you intend not to use the above two scripts to customize your JumpStart environment.

    Note –

    If you do not have your own specific begin or postinstallation scripts skip to step 4.

    Note –

    If you have your own specific begin or postinstallation scripts incorporate the begin_js.sh functionality in your begin scripts and postinstall.sh functionality into your postinstallation scripts.

  4. Create the following files with the following content for each file:


    cat /images/jumpstart-sparc/profile.sparc


    install_type initial_install
     cluster SUNWCXall
     partitioning explicit
     filesys any free /
    		 

    cat /images/jumpstart-sparc/rules


    arch sparc begin_js.sh profile.sparc postinstall.sh
    		 

    cat /images/jumpstart-sparc/sysidcfg


    system_locale=en US
     timezone=US/Pacific
     timerserver=localhost
     terminal=xterm
     name_service=NONE
     security_policy=NONE
     root_password=WPUDTTMUiG2JI
     network_interface=primary {
             default_route=10.42.42.1 
             netmask=255.255.255.0 protocol_ipv6==no
     }

  5. Make any other specific JumpStart customizations that you might want to have. See the Solaris 9 12/03 Installation Guide for details on how a JumpStart server can be configured.

  6. Validate the files using the check script. 


    cd /images/jumpstart-sparc
/images/s9u5s/Solaris_9/Misc/jumpstart_sample/check

  7. Ensure that you profile access to the resource pool server through rsh by issuing the following commands:


    cd /image/9su5s/Solaris_9/Tools/Boot
echo "+" > .rhosts

  8. Ensure that a proper boot environment is setup for the platform name and group by issuing the following command: 


    add_install_client -d -s
Solaris-install-server-ip-address:Solaris-product-directory -c 
JumpStart-server-ip-address:JumpStart-directory -p 
Jumpstart-Configuration-server-ip-address:Jumpstart-Configuration-directory 
platform_name platform_group
    Note –

    See the add_install_client -d -s for details.

    1. When you install the N1 Provisioning Server software, you specify the image subnet. So when using the N1 Provisioning Server as your JumpStart server, use the IP address on the image subnet. To determine what image IP address the N1 Provisioning Server is using, run the command ifconfig -a to get a list of interfaces and their IP addresses. Look for the IP address that is on the image subnet.

      Example:


      /images/s9u5s/Solaris_9/Tools/add_install_client -d -s 
10.42.42.1:/images/s9u5s -c 10.42.42.1:/images/jumpstart-sparc -p 
10.42.42.1:/images/jumpstart-sparc SUNW.Serverblade1 sun4u
      Note –

      Each time you run add_install_client you are changing the boot file used for booting hardware of the specified platform_name and platform_group. The resource pool server will boot from the boot file that was setup by the last add_install_client command.

  9. The image command supports the following set of DHCP options:

    • SrootOpt

    • SrootIP4

    • SrootNM

    • SrootPTH

    • SswapIP4

    • SswapPTH

    • SbootFIL

    • Stz

    • SbootRS

    • SinstIP4

    • SinstNM

    • SinstPTH

    • SsysidCF

    • SjumpsCF

    • Sterm

    See the Preconfiguring System Configuration Information section of the Solaris 9 12/03 Installation Guide for more information on the DHCP options.

    Following are the contents of the DHCP options file for the example JumpStart configuration created in this procedure:


     cat dhcp-options.txt
     SinstNM 10.42.42.1
     SinstPTH /image/s9u5s
     SrootNM 10.42.42.1
     SinstIP4M 10.42.42.1
     SinstPTH /images/s9u5/Solaris_9/Tools/Boot
     SsysidCF 10.42.42.1:/images/jumpstart
     SjumpsCFF 10.42.42.1:/images/jumpstart
    Note –

    The image server IP address is used for the root server, installation server, and JumpStart configuration.

ProcedureTo Customize the Boot and Configuration Server for the x86 Architecture

Steps

  1. Create the JumpStart directory on image server.

    Example:


    mkdir -p /images/jumpstart-x86

  2. Verify that the path to the JumpStart directory is shared appropriately by typing:


    share | grep /images/jumpstart-x86

    If the path is displayed and anon=0 is displayed in the options, proceed to the next step. If the path is not displayed or you do not have anon=0 in the options, continue with this step.

    1. Make the JumpStart directory NFS shared by adding the following entry to the /etc/dfs/dfstab file. 


      share -F nfs -o anon=0,rw=@10.42.42.0/24 -d "jumpstart server directory x86" 
/images/jumpstart-x86

    2. Make sure the JumpStart server's directory path is correctly shared.


      ps -ef | grep nfsd

      If the nfsd daemon is not running, start it by typing /etc/init.d/nfs.server start.

      If the nfsd daemon is running, share the JumpStart server by typing shareall.

  3. Use the following two scripts to customize the JumpStart begin and postinstallation for N1 Provisioning Server and copy them to the JumpStart directory:


    cp /tftpboot/terraspring/jumpstart/profiles/begin_js.sh 
/images/jumpstart-x86
cp /tftpboot/terraspring/jumpstart/profiles/postinstall.sh /images/jumpstart-x86

    See Customizing the Resource Pool Server Manually if you intend not to use the above two scripts to customize your JumpStart environment.

    Note –

    If you do not have your own specific begin or postinstallation scripts skip to step 4.

    Note –

    If you have your own specific begin or postinstallation scripts incorporate the begin_js.sh functionality in your begin scripts and postinstall.sh functionality into your postinstallation scripts.

  4. Create the following files with the following content for each file:


    cat /images/jumpstart-x86/profile.x86


    install_type initial_install
     cluster SUNWCXall
     partitioning explicit
     filesys any free /
    		 

    cat /images/jumpstart-x86/rules


    arch i386 begin_js.sh profile.x86 postinstall.sh
    		 

    cat /images/jumpstart-x86/sysidcfg


    system_locale=en US
     timezone=US/Pacific
     timerserver=localhost
     terminal=dtterm
     keyboard=UNKNOWN
     display=UNKOWN
     pointer=UNKNOWN
     monitor=UNKNOWN {
              DisplayChksum=0x0
     }
     root_password=WPUDTTMUiG2JI
     name_service=NONE
     security_policy=NONE 
     network_interface=PRIMARY {
                default_route=10.42.42.1 
                netmask=255.255.255.0 protocol_ipv6==no
     }

  5. Make any other specific JumpStart customizations that you might want to have. See the Solaris 9 12/03 Installation Guidefor details on how a JumpStart server can be configured.

  6. Validate the files using the check script.

    Note –

    Run the check command from the same Solaris distribution.


    cd /images/jumpstart-x86
s9u5x/images/s9u5x/Solaris_9/Misc/jumpstart_sample/check

  7. Ensure that you profile access to the resource pool server through rsh by issuing the following commands:


    cd /image/s9u5s/Solaris_9/Tools/Boot
echo "+" > .rhosts

  8. Ensure that a proper boot environment is setup for the platform name and group by issuing the following command: 


    add_install_client -d -s
Solaris-install-server-ip-address:Solaris-product-directory -c 
JumpStart-server-ip-address:JumpStart-directory -p 
Jumpstart-Configuration-server-ip-address:Jumpstart-Configuration-directory 
platform_name platform_group
    Note –

    See the add_install_client -d -s for details.

    1. When you install the N1 Provisioning Server software, you specify the image subnet. So when using the N1 Provisioning Server as your JumpStart server, use the IP address on the image subnet. To determine what image IP address the N1 Provisioning Server is using, run the command ifconfig -a to get a list of interfaces and their IP addresses. Look for the IP address that is on the image subnet.

      Example:


      /images/s9u5x/Solaris_9/Tools/add_install_client -d -s 
10.42.42.1:/s9u5x/images/s9u5x -c 10.42.42.1:/images/jumpstart-x86 -p 
10.42.42.1:/images/jumpstart-x86 SUNW.i86pc i86pc
      Note –

      Each time you run add_install_client you are changing the boot file used for booting hardware of the specified platform_name and platform_group. The resource pool server will boot from the boot file that was setup by the last add_install_client command.

  9. The image command supports the following set of DHCP options:

    • SrootOpt

    • SrootIP4

    • SrootNM

    • SrootPTH

    • SswapIP4

    • SswapPTH

    • SbootFIL

    • Stz

    • SbootRS

    • SinstIP4

    • SinstNM

    • SinstPTH

    • SsysidCF

    • SjumpsCF

    • Sterm

    • BootFile

    • SbootURI

    See the Preconfiguring System Configuration Information section of the Solaris 9 12/03 Installation Guide for more information on the DHCP options.

    The following is a sample DHCP options file for the example JumpStart configuration created in this procedure.


     cat dhcp-options.txt
     SinstNM 10.42.42.1
     SinstPTH /image/s9u5x
     SrootNM 10.42.42.1
     SinstIP4M 10.42.42.1
     SinstPTH /images/s9u5x/Solaris_9/Tools/Boot
     SsysidCF 10.42.42.1:/images/jumpstart-x86
     SjumpsCFF 10.42.42.1:/images/jumpstart-x86
     BootFile nbp.SUNW.i86pc
     SSbootURI tftp://10.42.42.1/SUNW.i86pc
    Note –

    The image server IP address is used for the root server, installation server, and JumpStart configuration.