Scribd Logo
Upload

Welcome to Scribd!

  • 73 views

    Presentation On Jumpstart (Remote Un-Attendant Installation)

    Uploaded by

    Shweta Gupta
    This presentation discusses how to set up and use Jumpstart, a Solaris tool for remotely installing the operating system over a network to multiple servers. It involves setting up an install or boot server with the OS media image and client configuration files. The process then connects clients through the network to install the OS. Key steps include preparing the install server, setting up configuration files like sysidcfg and profiles, adding client information, and troubleshooting installation issues.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Presentation On Jumpstart (Remote Un-Attendant Installation)

    Uploaded by

    Shweta Gupta
    73 views13 pages
    This presentation discusses how to set up and use Jumpstart, a Solaris tool for remotely installing the operating system over a network to multiple servers. It involves setting up an install or boot server with the OS media image and client configuration files. The process then connects clients through the network to install the OS. Key steps include preparing the install server, setting up configuration files like sysidcfg and profiles, adding client information, and troubleshooting installation issues.

    Original Title

    Jumpstart Server Configuration1

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This presentation discusses how to set up and use Jumpstart, a Solaris tool for remotely installing the operating system over a network to multiple servers. It involves setting up an install or boot server with the OS media image and client configuration files. The process then connects clients through the network to install the OS. Key steps include preparing the install server, setting up configuration files like sysidcfg and profiles, adding client information, and troubleshooting installation issues.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    73 views13 pages

    Presentation On Jumpstart (Remote Un-Attendant Installation)

    Uploaded by

    Shweta Gupta
    This presentation discusses how to set up and use Jumpstart, a Solaris tool for remotely installing the operating system over a network to multiple servers. It involves setting up an install or boot server with the OS media image and client configuration files. The process then connects clients through the network to install the OS. Key steps include preparing the install server, setting up configuration files like sysidcfg and profiles, adding client information, and troubleshooting installation issues.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    You are on page 1of 13

    Presentation on Jumpstart (Remote Un-attendant Installation)

    By: Mohammad Shamim

    Jumpstart
    Server in Solaris enables installation of OS over network to multiple range of servers differing in architecture ,softwares, packages, disk capacity etc. The process consists of setting up of a boot server/install server with OS media image and jumpstart client configurations and connecting clients through network

    Training Contents
    Before You start Preparing for Jumpstart server Setting up an Install server Setting up boot server Setting up configuration Files sysidcfg file Creating Profiles Making Rules Verifying Rules Adding a host entry Adding a client Starting the client installation Begin and Finish scripts Trouble Shooting

    Before you start


    Make sure The install server or boot server is in the same local network segment as client with network link up. NFS services are running On jumpstart server The tftp services are running. To start uncomment the tftp entry in /etc/inet/inetd.conf and restart the inet services The reverse address lookup daemon ,in.rarpd , is running. rpc.bootparamd daemon should be running.

    Setting up an Install Server

    make directory to store install server data. # mkdir /export/install share it # vi /etc/dfs/dfstab add share -F nfs -o ro,anon=0 /export/install to export file system for sharing. Do a shareall so that the file system is now exported Setting up an Install server Mount Solaris 10 DVD or cdrom Follow the steps : # cd /cdrom/cdrom0/Solaris_10/Tools #./setup_install_server /export/install This will copy the cdrom contents in to the /export/install directory.

    Setting up a boot server


    For installing clients over different networks you need a boot server in the same subnet as client . Boot server after booting the client hands over subsequent installation & configuration process to install server .

    # ./setup_install_server -b /export/install sun4u

    the above command installs software for booting the client. You also have to do a add host and add_install_client in boot server, see adding clients . Rest of the configuration has to be done at install server

    Setup Configuration Server


    Make a Directory where we want to keep Answer files. # mkdir /jumpstart Copy the Template data from the Media # cp r /cdrom/cdrom0/Solaris_10/Misc/* /jumpstart

    Creating sysidcfg
    Create one file as sysidcfg which contains all the configuration details of Client. # vi /jumpstart/sysidcfg
    keyboard=US-English system_locale=en_US timezone=Asia/Calcutta security_policy=none name_service=none terminal=vt100 timeserver=localhost nfs4_domain=dynamic root_password=cdNFLIX.k.RJs network_interface=e1000g0 {hostname=MITSERVER ip_address=172.16.250.178 netmask=255.255.255.0 protocol_ipv6=no default_route=172.16.250.1}

    Setup Configuration Server


    Create another file which having profile information. # vi /jumpstart/profile
    install_type initial_install partitioning explicit filesys c1t0d0s0 25600 filesys c1t0d0s1 32768 filesys c1t0d0s5 15360 filesys c1t0d0s6 10240
    / swap /var /export/home

    Create one file named as rules # vi /jumpstart/rules


    hostname MITSERVER - profile Then run the check script which validate your profile file.

    # ./check
    Validating rules... Validating profile profile... The custom JumpStart configuration is ok.

    Adding Host Entry


    We need to add hostname and IP address entry of the Client on /etc/hosts # vi /etc/hosts
    192.168.250.178 MITSERVER

    One hostname and Ethernet ID entry require under /etc/ethers # vi /etc/ethers


    00:12:4d:fb:11:32 MITSERVER

    For Updating /etc/bootparam file we need to run one Script as below. # cd /export/jumpstart/Solaris_10/Tools # ./add_install_client -p 192.168.250.11:/jumpstart -c 192.168.250.11:/jumpstart MITSERVER sun4v /etc/bootparam file automatically updated as per options you supply with add_install_client

    Starting the client installation


    Bring the Server in OK Prompt. And Start the Installation as below.
    Ok> boot net install
    the system will initialize and starts booting from network and you will see these messages System is coming up checking rules file using profile any _machine selecting cluster SUNWCall Preparing system to install software setting up disk creating and checking up file systems

    installing packages

    Begin & Finish Scripts


    These are the optional features of jumpstart . A begin script is a shell script which is used to perform the task before Solaris OS is installed. These are specified in the rules file. These can be used for creating dynamic derived profiles or backing up files before upgrading. A finish script is used to perform the tasks after the OS is installed but before reboot. These can be used to customize root environment , adding patches , files etc. These scripts can not be checked by the check script so it must be accurate. Out put of these scripts goes to /var/adm/begin.log and finish.log. These should be owned by the root with permission 644

    Trouble Shooting
    Error : unknown client "client host name"
    Source : add_install_client Cause : host name can't be resolved . check host entry is there in /etc/ethers or in nis/nis+ maps . Source : Solaris booting process Cause : Improper media . Make sure proper media is available through disk image or CD in the install server . Also see that the rules point to valid media type. Source: Client boot requests Cause : Muliple entries for a client in different servers. There should not be multiple entries in different install server's /etc/bootparams , /tftpboot or /rplboot . These causes a hang situation when all of them try to answer.

    File just loaded does not appear to be executable .

    Warning : getfile:RPC failed : error 5 (RPC timed out)


    No network boot server .Unable to install the system. See installation instructions
    Source : Client boot request. Cause : Installation is not proper. Check the boot server installation again for any error in command or file . Source : Client boot request . Cause : No server is answering its request for booting .Probably they don't know about this client . See the proper entries are there in /etc/bootparams or nis maps with proper entries in nsswitch.conf . add_install_client is responsible for adding client information in jumpstart server so check the command and its option..

    Timeout waiting for ARP/RARP packet

    Thank You

    You might also like