Sun Management Center 4.0 Installation and Configuration Guide

ProcedureTo Add Install Client Information to the JumpStart Server

  1. Log in as root on the JumpStart server.

  2. Insert the Solaris installation CD 1 of 2 in your CD-ROM drive.

    Go to the Tools directory on the CD.


    # cd /DiskMountDir/s0/Solaris_2.8/Tools
    
  3. Determine the system identification information for each install client.

    The JumpStart server requires the following information about each install client.

    • Name

    • Ethernet address

    • IP address

    • Architecture

    Log on to each install client, and use the arp and uname commands as follows to display the install client's Ethernet address, IP address, name, and architecture.


    > arp clienthost
    clienthost (111.222.123.124) at 8:0:80:e4:23:eb permanent published
    > uname -a
    SunOS clienthost 5.9 Generic_112233-01 sun4u sparc SUNW

    In the above example, the clienthost install client Ethernet address is 8:0:80:e4:23:eb, the IP address is 111.222.123.124, and the architecture is sun4u.

  4. Add the system identification information for each install client to the JumpStart server.

    The add_install_client command is used to add the install client information to the JumpStart server as follows:


    add_install_client \
    -c JumpStart_profile_server:path_to_configuration_directory \
    -s JumpStart_install_server:path_to_operating_environment_image \
    -p JumpStart_profile_server:path_to_SYSIDCFG_file \
    -e install_client_ethernet_address \
    -i install_client_IP_address \
    install_client_name install_client_architecture
    

    For example, assume your systems are configured as follows.

    • Machine bootserver01 is your JumpStart boot server, profile server, and install server.

    • The JumpStart configuration directory on bootserver01 is /export/home/JumpStart/jumpstart.

    • The JumpStart operating environment image directory on bootserver01 is /export/home/JumpStart/Solaris_9.

    • The system identification configuration file sysidcfg is located in the JumpStart configuration directory /export/home/JumpStart/jumpstart.

    • The install client Ethernet address is 8:0:80:e4:23:eb, and the IP address is 111.111.123.124.

    • The install client's name is clienthost, and the install client's architecture is sun4u.

    You would then add the install client clienthost using the add_install_client command as follows.


    # ./add_install_client -c bootserver01:/export/home/JumpStart/jumpstart \
      -s bootserver01:/export/home/JumpStart/Solaris_9 \
      -p bootserver01:/export/home/JumpStart/jumpstart \
    -e 8:0:80:e4:23:eb -i 111.111.123.124 \
      clienthost sun4u 
      Adding Ethernet number for clienthost to /etc/ethers
      making /tftpboot
      enabling tftp in /etc/inetd.conf
      starting rarpd
      starting bootparamd
      updating /etc/bootparams
      copying inetboot to /tftpboot

    When you have finished adding install client system information to the JumpStart server, you can then use JumpStart to install the Solaris operating environment and the Sun Management Center base agent as described in the next step.

    For further information about the add_install_client command and options, see the man page add_install_client(1m).

  5. Boot each install client.

    1. Logon as root on the client machine in single-user mode.

    2. At the ok prompt, type the command boot net - install.

      For example:


      {2} ok boot net - install
      

      The client system boots from the JumpStart server. JumpStart installs the Solaris operating environment specified by the JumpStart profile assigned to the install client by the applicable rule in the rules file. When the operating environment has been installed, the Sun Management Center 4.0 base agent is installed. The install client then reboots.

      When the install client reboot completes, the Sun Management Center base agent is set up according to the specifications of the finish script assigned to the install client by the applicable rule in the rules file. If you hard coded the security password seed and the SNMP community string in the finish script, base agent setup is automatic. If you chose not to hard code the password seed and community string in the finish script, you must respond to the base agent setup prompts on each install client to complete base agent setup.