InfoDoc ID   Synopsis   Date
41340   Creating a Boot server for a Netra (TM) X1   20 Mar 2002

Status Issued

Description

The purpose of this document is to demonstrate how to create a Boot server for a Netra (TM) x1 server. The Netra x1 installation method prior to Solaris (TM) 8 U7 (2/02) Operating Environment requires installation from a network install server. This installation process is documented in INFODOC 26310, it requires that the install image be modified from the mis.netra-x1.259-3836-03 script. The mis.netra-x1.259-3836-03 script does not run successfully on a Boot server. A Boot server is required if the Netra x1 client will be installing from a different subnet than from that of the Install server.

The Netra x1 drivers will be integrated into Solaris 8 Update 7 (2/02). At that time the standard method of creating a boot server or install server can be utilized (reference the Advanced Installation Guide).

Prior to using this procedure, the Install server must be created per INFODOC 26310. The Boot server and Install server image must be the same Solaris 8 update release. This example uses Solaris 8 update 5 (7/01).

Objective: Copy (tar) a Netra x1 modified Boot directory from the existing Install server to the Boot server.

On the Boot Server:

1) Verify your Boot server disk space can accommodate approximately 255mb:

# df -k /Images
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c0t1d0s0    8513156 5038704 3389321    60%    /Images                              

2) Insert the Solaris 8 software CD 1 of 2, change directory to the Tools directory and execute "setup_install_server -b /path_to_boot_image" where:

setup_install_server = the installation script

-b = option to create a boot server

/path_to_boot_image = a unique empty directory for the boot image

# cd /cdrom/cdrom0/s0/Solaris_8/Tools

# ./setup_install_server -b /Images/Boot_U5_netra.x1
Verifying target directory...
Calculating space required for the installation boot image
Copying Solaris_8 Tools hierarchy...
Install Server setup complete                              

Note: The size of this boot image is 252444k

# du -sk /Images/Boot_U5_netra.x1
252444                                

Note: The size of a just the Boot directory is 252330k

# du -sk /Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot
252330                                

Note: A boot directory modified for a Netra x1 is 252623k

3) Remove the unmodified Boot directory:

# cd /Images/Boot_U5_netra.x1/Solaris_8/Tools
# rm -r Boot
      

Note: Removing just the Boot file preserves the other files and directories that were created via "setup_install_server -b".

                             

On the Install Server:

1) Change directory to the Boot directory of the Solaris 8 U5 (7/01) install image:

# cd /image_28/U5.netra.x1/Solaris_8/Tools/Boot                              

2) Use tar to copy this directory to the Boot server:

# tar cvBf - . | rsh 129.148.11.7 "cd /Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot; tar xvBf -"                              

On the Boot Server:

3) Verify the boot directory copied successfully by comparing its size to the source Boot directory size:

# du -sk /Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot
252623                                

4) Create the client via the add_install_client command, the -s switch must point to the install server. In this example this is also where the sysidcfg file and jumpstart configuration directory is located and therefore the -p and -c switches were used (jumpserver-11net is the Install server in this example):

# ./add_install_client -s jumpserver-11net:/image_28/U5.netra.x1 -p jumpserver-11net:/jumpstart/sysidcfg.sol8 -c jumpserver-11net:/jumpstart ib-x1 sun4u
Adding "share -F nfs -o ro,anon=0 /Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot" to /etc/dfs/dfstab
updating /etc/bootparams                              

On the Netra x1:

1) Boot the Netra x1

ok boot net - install

                              

INTERNAL SUMMARY:

Internal Summary

This is only internal as to not clutter the document. There shouldn't be any secret here.

rpc.bootparamd in debug mode (/usr/sbin/rpc.bootparamd -d) shows access through the boot server (jumpserver-11net-old), then the Install server (jumpserver-11net):

Whoami returning name = ib-x1, router address = 129.148.11.248
getfile_1: file is "jumpserver-11net-old" 129.148.11.7 "/Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot"

Whoami returning name = ib-x1, router address = 129.148.11.248
getfile_1: file is "jumpserver-11net-old" 129.148.11.7 "/Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot"
getfile_1: file is "" 0.0.0.0 "rsize=32768"
getfile_1: file is "jumpserver-11net-old" 129.148.11.7 "/Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot"

Whoami returning name = ib-x1, router address = 129.148.11.248
getfile_1: file is "jumpserver-11net-old" 129.148.11.7 "/Images/Boot_U5_netra.x1/Solaris_8/Tools/Boot"
getfile_1: file is "jumpserver-11net" 129.148.11.1 "/image_28/U5.netra.x1"
getfile_1: file is "jumpserver-11net" 129.148.11.1 "/jumpstart/sysidcfg.sol8"
getfile_1: file is "jumpserver-11net" 129.148.11.1 "/jumpstart"
                              

Also reference Bug Id: 4493374

SUBMITTER: Paul Buckley APPLIES TO: AFO Vertical Team Docs/Install/Boot ATTACHMENTS:


Copyright (c) 1997-2003 Sun Microsystems, Inc.