Sponsored Content
Operating Systems Solaris Automate Solaris x86 Jumpstart Post 302330582 by racbern on Wednesday 1st of July 2009 05:14:20 PM
Old 07-01-2009
Automate Solaris x86 Jumpstart

Hi All,

Is there a possible way to fully automate Solaris x86 jumpstart or make the x86 jumpstart unattended?

I'm currently checking the possible options on how can I do the x86 jumpstart to be kicked off during midnight.

We have an automated jumpstart (start to run from midnight) for Solaris 10 sparc, wherein we implemented it with shell script + expect script to pass the parameters and boot args, and Im looking at the possibility of doing this for Solaris 10 x86 as well.

Any insights are well appreciated on which scripting mechanism (ie. expect script) I need to use to automate the connection to ILOM? Load the GRUB Menu and choose option from the GRUB Menu?

Thanks in advance.
//racbern
 

9 More Discussions You Might Find Interesting

1. Solaris

Jumpstart on x86 client- prompt for CD2

Hi I just configured a jumpstart server for x86 and sparc clients. I don't use a dhcp server, so I configured /etc/ethers and did add_install_client to update /etc/bootparams. The sparc installation ist working, but the x86 installation stops after CD1 was successfully installed. What I did: I... (2 Replies)
Discussion started by: Jay_Fisi
2 Replies

2. Solaris

Jumpstart Solaris 10 x86

I need a little help figuring out why my custom jumpstart network installation is dumping me to a manual install. I am trying to install Solaris 10 (unattended) over the wire from my jumpstart server to an HP Proliant DL380 server but I'm having difficulties with the unattended part. So, what... (2 Replies)
Discussion started by: alias.256
2 Replies

3. Solaris

Solaris 10 x86 Jumpstart w/o GUI

Does anyone know how to Jumpstart a Solaris 10 x86 system without the GUI? I would like to keep the Jumpstart and/or Flash Archive install in a console text mode if possible but I've not had much luck finding instructions. I'm guessing this is going to be accomplished from the grub menu with a... (5 Replies)
Discussion started by: alias.256
5 Replies

4. Solaris

One time network boot of Jumpstart x86 client

I am trying to find an approach that has been effective for automating the installation of Solaris 10 x86 using Jumpstart technology. I have configured an Jumpstart server and a Solaris dhcp server with appropriate macros for passing the client information about its boot environment. The problem is... (7 Replies)
Discussion started by: chajo19
7 Replies

5. Solaris

Jumpstart sparc client using x86 server.

Can I use a Jumpstart enviroment on x86 to install a sparc64 client? The idea is to install Solaris in an virtual environment (Sun Virtual Box) running on a pc (AMD), configure a Jumpstart server, and have a SUN Ultra 60 (sparc64) installed via the Jumpstart server. The SUN has no cdrom... (4 Replies)
Discussion started by: eldiablo
4 Replies

6. Solaris

Jumpstart Installation from X86 machine

Hi friends , i have on ultra 10 Sparc machine . Due to some problem my OS is fully corrupted , so i am planning to install again but my problem is the cd drive in Ultra 10 machine is not working. Now i am planning to use Jumpstart installation method to install my server. But i... (4 Replies)
Discussion started by: vr_mari
4 Replies

7. Solaris

custom jumpstart on x86 with DHCP/PXE goes into interactive mode

client boots fine, it gets the ip 192.168.0.10 and the bootfile. Then there is : SunOS 5.10 Version Generic_141445-09 32-bit" ... Configuring devices. Custom JumpStart Reading ZFS config: done Setting up Java. Please wait ... NOTE: Not enough memory for graphical installation. Graphical... (4 Replies)
Discussion started by: TomSu
4 Replies

8. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

9. Solaris

Installing Solaris x86 using jumpstart does not set the hostname for the target

Installing Solaris x86 using jumpstart does not set the hostname for the target. Any idea where do we need to specify hostname to be set for jumpstart installation. (1 Reply)
Discussion started by: hemalsid
1 Replies
bootadm(1M)						  System Administration Commands					       bootadm(1M)

NAME
bootadm - manage bootability of GRUB-enabled operating system SYNOPSIS
/sbin/bootadm update-archive [-vn] [-R altroot [-p platform]] /sbin/bootadm list-archive [-vn] [-R altroot [-p platform]] x86 only /sbin/bootadm set-menu [-R altroot [-p platform]] key=value /sbin/bootadm list-menu [-R altroot [-p platform]] DESCRIPTION
The bootadm command manages the boot archive and, with x86 boot environments, the GRUB (GRand Unified Bootloader) menu. The update-archive option provides a way for user to update the boot archive as a preventative measure or as part of a recovery procedure. The set-menu sub- command allows you to switch the auto-boot timeout and default boot entry in the GRUB menu. The list-menu subcommand displays the location of the GRUB menu and the current GRUB menu entries. While the typical location of the GRUB menu is /boot/grub/menu.lst, depending on the install method used the active GRUB menu might be located somewhere else. Use the list-menu subcommand to locate the active GRUB menu. For example, if a system was installed using Live Upgrade, the GRUB menu might not be located in the current boot environment. See the EXAMPLES section for typical output from the list-menu option. Note that OpenBoot PROM (OBP)-based machines, such as SPARC systems, do not use GRUB and have no boot menu manageable by bootadm. The bootadm command determines dynamically the options supported by the image to be managed, so that bootadm invoked on one platform can be used to manage diskless clients of a different platform type. SUBCOMMANDS
The bootadm command has the following subcommands: update-archive Updates current boot archive if required. Applies to both SPARC and x86 platforms. list-archive Lists the files and directories to be included in the boot archive. Applies to both SPARC and x86 platforms. set-menu Maintain the GRUB menu. The current GRUB menu is boot/grub/menu.lst, relative to root. Do not depend on this location, because it is subject to change. Applies to x86 platforms only. list-menu Lists the location of the active GRUB menu, as well as the current GRUB menu entries. This includes the autoboot-timeout, the default entry number, and the title of each entry. Applies to x86 platforms only. OPTIONS
The bootadm command has the following options: -v In an update-archive operation, stale files are displayed on stderr. -n In an update-archive operation, archive content is checked but not updated. -p platform The platform, or machine hardware class, of the client. The platform type can only be specified together with -R, and is generally use- ful only for managing a diskless client where the client is of a different platform class than the server. Platform must be one of i86pc, sun4u, or sun4v. -R altroot Operation is applied to an alternate root path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). key=value Possible values are: default=entrynum The item number (for example, 0, 1, or 2) in the GRUB menu designating the operating system to boot when the timer expires. timeout=seconds The number of seconds before the operating system designated by the default item number is booted. If the value is -1, auto boot is disabled. EXAMPLES
Example 1 Updating the Current Boot Archive The following command updates the current boot archive: # bootadm update-archive Example 2 Updating the Boot Archive on an Alternate Root The following command updates the boot archive on an alternate root: # bootadm update-archive -R /a Example 3 Listing Installed OS Instances The following command lists the installed operating system instances in a GRUB menu: # bootadm list-menu default=0 timeout=10(0) Solaris10(1) Solaris10 Failsafe(2) Linux Example 4 Switching Default Boot Entry The following command refers to the menu displayed in the previous example. The user selects Linux (item 2). # bootadm set-menu default=2 Example 5 Listing GRUB Menu Entries and Location of GRUB Menu The following command lists the GRUB menu entries and the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst default 0 timeout 10 0 Solaris10 1 Solaris10 failsafe 2 Linux Example 6 Displaying Location of GRUB Menu The following command displays the location of the GRUB menu: # bootadm list-menu The location for the active GRUB menu is: /dev/dsk/c0t1d0s0 (not mounted) The filesystem type of the menu device is <ufs> default 2 timeout 10 0 c0t1d0s3 1 c0t1d0s3 failsafe 2 Solaris10 3 Solaris10 failsafe In this example, the active GRUB menu is located on a device which is not mounted. To access the GRUB menu, mount the device and access the GRUB menu at <mountpoint>/boot/grub/menu.lst. EXIT STATUS
The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
boot(1M), installgrub(1M), attributes(5) Consult the GRUB home page, under: http://www.gnu.org/ SunOS 5.11 25 Apr 2008 bootadm(1M)
All times are GMT -4. The time now is 10:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy