SUMMARY: howto to setup a basic jumpstart server

From: António Vasconcelos <antonio.vasconcelos_at_all2it.pt>
Date: Fri Mar 04 2005 - 06:06:27 EST
I had a Fire 240 with a broken CD/DVD drive and needed to install 
Solaris ASAP.
Maybe some one will find this usefull

-- 

Antsnio  Vasconcelos
/(Administrador de Sistemas)
ALL2IT-Infocomunicagues, SA
Torre de Monsanto, 6: Piso
Miraflores, Algis
PORTUGAL
Telf.: + 351 21 412 39 50
Fax.: + 351 21 410 51 94/

 

*CONFIDENCIAL*: Esta mensagem contim informagco confidencial ou material 
privilegiado, e i ss intencionada para os seus destinatarios. De acordo 
com a lei em vigor, se um erro originou que tenha recebido esta mensagem 
por engano pedimos que, de imediato, notifique o remetente e a apague do 
seu sistema sem a reproduzir.
	*CONFIDENTIAL*: This e-mail contains proprietary information, some or 
all of which may be legally privileged. It is for the intended 
recipients only. According to the law in force, if an addressing or 
transmission error has misdirected this e-mail, please notify the author 
by replying to this e-mail and delete it from your system without 
retaining a copy.
****************************************************
****************************************************
*** How to do a SIMPLE Solaris 9 Network Install ***
****************************************************
****************************************************

This   procedure   does   not  cover  any   kind   of  jumpstart   customization
neither unattended installation.

Problem: Sun Fire V240 with a  dead CD/DVD drive and need to  re-install Solaris
9, ASAP.

Tools: A   network connection,   another  Sun   with about   1.1 Gigabytes  disk
free, Solaris 9 CD #1 and #2

Note#1: The  Sun that will  have the server  don't need to  be running the  same
Solaris version, on my case the server was running Solaris 8.

Note#2: This will  produce an interactive  installation, just like  what you get
if you boot from the CD to do the install.

*******************************************************************************
a)  Preparing the server
*******************************************************************************

0- Decide where to store the files, for  Solaris 9 you need a tad more than  1.1
Gb for me it was /calendar/install_server/Solaris_9

1- Load and mount the Solaris 9 CD-ROM #1 (you should know how to do that)

2- Run the script to copy the CD to disk

    # cd /cdrom/cdrom0/s0/Solaris_9/Tools
    # ./setup_install_server /calendar/install_server/Solaris_9

    This will take some time, use the time for one or two large coffee cups...

3- Copy CD #2 to disk

    Eject CD #1, load and mount CD #2

    # cd /cdrom/cdrom0/Solaris_9/Tools
    # ./add_to_install_server /calendar/install_server/Solaris_9

    Time for another coffee

4- Configure the client on the server

    You'll need to know:

        - the MAC (ethernet) address of the machine you're installing
        - the IP address you want to configure on that machine
        - the hostname you want to configure on that machine
        - the machine hardware name (class) of the machine you are
          installing (uname -m)

        On this case:

            MAC addr -> 00:03:ba:3d:70:75
            hw name  -> sun4u (this is a sun fire 420)
            IP addr  -> 172.21.0.206
            hostname -> GRCSVR19

    For this case I didn't use any kind of name server, as I think that only NIS
    or NIS+ are supported  I did it without  one, so, the first  step was adding
    the hostname  of the  client to  the server's  /etc/hosts (without this step
    the add_install_client script will fail).
    Then running the script to configure the client.

    # cd /calendar/install_server/Solaris_9/Solaris_9/Tools
    # ./add_install_client -i 172.21.0.206 -e 00:03:ba:3d:70:75 GRCSVR19 sun4u

    This command will do a lot of things to your system

    - It setups NFS and shares the install dir:

    	/calendar/install_server/Solaris_9

      read only for everyone.

    - enables the tftp protocol on the server and creates /tftpboot, then copy
      some files to /tftpboot

      my /tftpboot now contains several files

        AC1500CE -> inetboot.SUN4U.Solaris_9-1
        AC1500CE.SUN4U -> inetboot.SUN4U.Solaris_9-1
        inetboot.SUN4U.Solaris_9-1
        rm.172.21.0.206
        tftpboot -> .


    - it updates the  file /etc/bootparams on my    case the   line was    (note
    #1:  tiktok  is  the  hostname  of the server),  (note #2:  all this  is  on
    just 1  line, I    added the  \ for  readability,  if the file  is  setup by
    hand the \  at the end of the  line can be used too):

 GRCSVR19  root=tiktok:/calendar/install_server/Solaris_9/Solaris_9/Tools/Boot \
 install=tiktok:/calendar/install_server/Solaris_9 \
 boottype=:in   rootopts=:rsize=32768

    - it starts up some  daemons that you may not  want to have running all  the
    time

      /usr/sbin/in.rarpd -a
      /usr/sbin/rpc.bootparamd

      and all the NFS stuff.

*******************************************************************************
b) Install the client
*******************************************************************************

    Go to the console, reboot the client  and break to the ok prompt. Then,  all
    you have to  do is type  "boot net - install". NOTE:  YES,  there is a SPACE
    between the "-" and the word "install".

    This is what happened on my case,  before starting I had made sure that  the
    network cable was connected and that the link leds showed activity.
    For some  time the  "ARP/RARP send  failed" made  me think  that it will not
    going to work  but I waited  a bit more  (about 5 minutes,  I think) and  it
    worked all ok.

    * ATTENTION ****************************************************************
    Some SUNs  when  connected  to some   switches brands  or models  have known
    problems while doing the  negotiation   of  the  ethernet link.  When   this
    happens,  the typical solution is to disable  auto-negotiation on the switch
    side and on the  Sun side, this  is done on the switch configuration and  in
    the /etc/system file.
    In this case you don't have an /etc/system file to tune as the interface  is
    being controlled  from the  boot prom  firmware, and  I'm not  sure if  it's
    possible to configure this parameters from the ok prompt.
    If instead of  the "1000 Mbps  FDX Link up"  message you see  one with "HDX"
    (the link  is on  Half-duplex) on  it    you  may expect  problems, from not
    working at all to a VERY slow link.
    If this happens I think it will be better to try to fix it before trying  to
    do the installation.

        {1} ok boot net - install

        Boot device: /pci@1f,700000/network@2  File and args: - install
        1000 Mbps FDX Link up
        Timeout waiting for ARP/RARP packet
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        ARP/RARP send failed.  Check Ethernet cable and transceiver.
        Timeout waiting for ARP/RARP packet
        Timeout waiting for ARP/RARP packet
        24000 1000 Mbps FDX Link up

        Requesting Internet address for 0:3:ba:3d:70:75
        SunOS Release 5.9 Version Generic_112233-05 64-bit
        Copyright 1983-2002 Sun Microsystems, Inc.  All rights reserved.
        Use is subject to license terms.
        Hardware watchdog enabled
        Configuring /dev and /devices
        Using RPC Bootparams for network configuration information.
        Skipping interface bge3
        Skipping interface bge2
        Skipping interface bge1
        Configured interface bge0
        Searching for configuration file(s)...
        Search complete.



        Select a Language

           0. English
           1. French
           2. German
           3. Italian
           4. Japanese
           5. Korean
           6. Simplified Chinese
           7. Spanish
           8. Swedish
           9. Traditional Chinese

        Please make a choice (0 - 9), or press h or ? for help: 0

    After this point  it will be  all like if  you're installing from  a CD. The
    only difference I noticed was that the IP address and netmask was not asked.

*******************************************************************************
c) Remove the Client Setup
*******************************************************************************

    After installation you  may want to  remove this setup,  I haven't tried  it
    yet, but the script:


    /calendar/install_server/Solaris_9/Solaris_9/Tools/rm_install_client

    should do that:

    # cd /calendar/install_server/Solaris_9/Solaris_9/Tools
    # ./rm_install_client GRCSVR19


--
version 1.0
2005.03.02
Antonio Vasconcelos
ae.vasconcelos[a]gmail.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Fri Mar 4 06:07:06 2005

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:44 EST