How to Use the Command-Line Interface to Automate Setup Tasks

1. Convert a standalone system to an OS server.

   % admhostmod -x type=os_server rogue

2. Add OS services to the OS server.

   1. This example adds the Solaris 2.5 End User Cluster OS services for the Sun4m kernel architecture to rogue. The Solaris CD image is on a mounted CD on a remote system named jupiter. Note that the remote system must be minimally set up as a managed system.

      % admhostmod -x mediapath=jupiter:/cdrom/cdrom0/s0 \ -x platform=sparc.sun4m.Solaris_2.5 -x cluster=SUNWCuser \ rogue

   2. This examples adds the Solaris 2.5.1 All Cluster OS services for the Sun4m kernel architecture to rogue. The Solaris CD image has been copied to hard disk on a remote system, saturn, and the automounter is used to access it. Note that the remote system must be minimally set up as a managed system.

      % admhostmod -x mediapath=rogue:/net/saturn/export/Solaris_CD \ -x platform=sparc.sun4m.Solaris_2.5.1 -x cluster=SUNWCall \ rogue

3. Add the AutoClient system.

   This example adds a Sun4m Solaris 2.5.1 AutoClient system named venus to the server rogue.

   % admhostadd -i 129.152.225.2 -e 8:0:20:b:40:e9 \ -x type=autoclient -x fileserv=rogue \ -x os=sparc.sun4m.Solaris_2.5.1 \ -x swapsize=40 -x diskconf=1disk -x diskconn=n venus

   You could use a similar version of this command in a shell script with additional operations to customize the AutoClient system's root as part of setting up the client. The script could be parameterized to accept the IP address, Ethernet address, and host name.