Post on 21-Jan-2016
transcript
Ignite-UX
Overview
Ignite-UX
Key Concepts
Ignite-UX
Detailed Presentation
ABCHP COMPANY CONFIDENTIAL
IUX Server
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
Process for initial system deployment True client-server model:
–can install multiple target machines simultaneously
–allows target customization and status monitoring
Ability to build and reuse standard configurations Ability to do site-specific customization Ability to automate installation process Extensible system manifest capability Ability to install software from multiple sources
in a single session!
What is Ignite-UX?
ABCHP COMPANY CONFIDENTIAL
IUX Server
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
IUX Target
Process for system re-deployment or SW upgrades All the same capabilities of previous NetInstall
deployment model! With the ability to target a previously installed
system on the network and reinstall it. Target a machine and have it reboot and give
control to the install server - bootsys Use the GUI to define what gets loaded or use a
“golden system” image GUI or command line control
What else is Ignite-UX?
ABCHP COMPANY CONFIDENTIAL
Cold Install Ignite-UX
Installation Methods
Install from Local media "Pull" Install from Network
Servers
Install from Local media "Pull" Install from Network
Servers "Push" Install from Network
Servers "Re-deploy" Existing
machines
Server Capability Serves Single Release that
Server is Running
Can Serve Multiple Releases (10.01 and forward)
User Interface TUI running on target TUI running on Target
GUI running on Server
Software Formats Software Distributor SD, cpio, tar
Multiple sources in one session
System Attributes Which Can Be Specified
A lot! Even more! More script hooks set_parms info
Produce a System Manifest
No Yes!
Ignite-UX versus Cold Install
ABCHP COMPANY CONFIDENTIAL
Ignite-UX SD
PurposeComplete installs of system software.
Manages software on an existing system.
Disk space considerations
Performs disk and file system layout.
Complains if it's short on disk space.
Objects handledHandles SD and other formats like tar or cpio, and even OS archives.
Knows about standard bundles, products and filesets.
Ignite-UX versus SD
ABCHP COMPANY CONFIDENTIAL
Ignite-UX is a tool which does the initial configuration and loading of an HP-UX system. At one time there were two different tools which accomplished this same task for different customer segments:
The CHAMP tool was used by HP manufacturers and two-tier distributors
The HP-UX Install program (also known as Cold Install) is used by end customers
Ignite-UX is designed as a replacement for both CHAMP and HP-UX Install. It will address the needs of both sets of customers.
Ignite-UX: A Tale of Two Tools
ABCHP COMPANY CONFIDENTIAL
HP Manufacturing High volumes of pre-installed HW & SWProduction line environment, high throughputHighly automated, no human interactionStandard configurations customizable via SISP
Two-tier distributors Medium-high volumesSmall unit ordersManual process via GUIMore customized configurations
High Volume Customers Small set of standard/certified configurationsCustomized to end user requirementsReinstallation of systems rather than updateInventory and IP address management
Low Volume Customers Often use ignited systemsNo need for standard configurationsInfrequent installs only on "as needed" basisSingle point access of system view
Customer Engineer Complex system installations at customer siteExtensive use of system diagnosticsHardware and software installation, network connectivityThird-party applications loaded
Segmentation of Ignite-UX Users
ABCHP COMPANY CONFIDENTIAL
HP Manufacturers Capability of high volume, standard OS bundle installsMinimal time per install, multiple simultaneous installsEase of linkage to OPHigh reliability
Two-tier Distributors Capability of high volume, standard OS bundle installsMinimal time per installUse multiple source formatsAdditional post-installation customization
High Volume Customers High volume installsCreate and install certified standard configurationsPerform post-installation customizationsQuery process and see configuration
Low Volume Customers Install from all sources (CD-ROM, DAT, network)Provide one-step installation from default configurationCustomize basic configuration parametersQuery process and see configuration
Customer Engineer Install from all sources (CD-ROM, DAT, network)Create and install standard configurationsProvide one-step installation from default configurationCustomize basic and advanced configuration parameters
Value Propositions for Ignite-UX Users
ABCHP COMPANY CONFIDENTIAL
Boot from local media–No Network Required
Run UI from the target's console
–TUI version of Server GUI interface (advanced) -or-
–Guided Tour of Selections (Wizard)
Target MachineCD
Tape
Cold Install from Local Media With Ignite-UX
ABCHP COMPANY CONFIDENTIAL
Do a 'boot lan install' from the client console
Run UI from target's console (like previous slide)
Use previously defined configs on server
Target Machine
Server
Network
Pull Cold Install from Network Server
ABCHP COMPANY CONFIDENTIAL
Initial screen on system console
Shows summary information Single client installation Normal mode is to select
Install HP-UX
Welcome to Ignite-UX!
ABCHP COMPANY CONFIDENTIAL
Permits choice of source location and user interface
Guided installation referred to as "wizard mode" which is not available in GUI
User Interface and Media Options
ABCHP COMPANY CONFIDENTIAL
Guided tour through recommended configuration choices
Does not allow file system size changes or setting networking parameters
Good for novice user
Basic itool screen: Wizard Mode
ABCHP COMPANY CONFIDENTIAL
Obam version of Ignite-UX interface
Tabbed windows look and feel
Basic itool screen: Advanced Mode
ABCHP COMPANY CONFIDENTIAL
Do a 'boot lan install' from client console (only interaction needed on client)
Run UI at the server Can do multiple clients at
once
Target Machines
Server
Network
Push Cold Install from Network Server
ABCHP COMPANY CONFIDENTIAL
Only necessary when doing a cold install of an unbootable machine across a gateway from server
Boot helper machine:–Must be running 10.*–Must install minimum Ignite-UX (Ignite-UX.MinimumRuntime)
–About 22Mb free–Point to server via instl_adm
On target:–b lan.<helper_ip_address> install–gets install kernel and RAMFS from helper, then connects to server
Not a relay agent
Subnet
Subnet
"Helper Machine"
Target Machine
Ignite-UX Server
Using Ignite-UX Across Gateways
ABCHP COMPANY CONFIDENTIAL
Useful when target machine is already running HP-UX 9.x or 10.x
Run bootsys on server:–Copies install kernel, fs down to target disk (uses remsh)
–Sets up target to boot from install kernel
–Reboots target–Target boots from disk and connects to server
No need to ever go to target console Network topology doesn't matter
Target Machine
Server
Gateway
Subnet
Subnet
Re-Deploy Existing Machine (bootsys)
ABCHP COMPANY CONFIDENTIAL
ClientTarget Customization
ServerCentral Control and Status
Monitoring
True Client-Server Application
ABCHP COMPANY CONFIDENTIAL
Icon per client being installed Colors used to indicate client
status Easily view status details of
any client Easily see detailed hardware
description of any client Reinstall option based on
saved install sessions Sort clients by name, status or
% complete Performs server configuration
tasks
IUX Server - Main Screen
ABCHP COMPANY CONFIDENTIAL
First screen to install a client
Easy selection of a base configuration from HP supplied defaults or a previously saved session
Provides for easy selection of basic configuration information
Designed to provide "GO" option from here
IUX Client - Basic Configuration
ABCHP COMPANY CONFIDENTIAL
Easily choose software packages to install
Software packages may be SD, tar or cpio formats
Can load multiple packages from multiple sources in a single session
Can select software category for filtering or easy package location
Categories can be HP or user defined
IUX Client - Software Options
ABCHP COMPANY CONFIDENTIAL
Allows easy setting of all system-specific parameters normally set as part of the first boot sequence
– Hostname, IP address, date, etc..
IUX Client - System Options
ABCHP COMPANY CONFIDENTIAL
Rich set of configuration options for setting up disks and file systems
Simpler screen for whole disk file systems
Sizes the file systems based on needs of the selected software
IUX Client - File System Options
ABCHP COMPANY CONFIDENTIAL
Allows easy selection of scripts to run after the installation is complete
– Allows for more unique system customization
– Even more script hooks available via the config file
IUX Client - Advanced Options
ABCHP COMPANY CONFIDENTIAL
Select a default configuration in UI:–e.g. "Default 10.20 Release"
Make modifications in the UI to select:–How you want disks/file systems allocated–What software you want installed–What scripts you want run–etc.
"Save As" to write your customized config file Optionally, hand edit the config file to make it
hardware independent:–Different disk layouts depending on what disks are present
–Swap space based on memory size–etc...
Save As...
Creating your own Customized Configurations
ABCHP COMPANY CONFIDENTIAL
Command & Script Hooks
System Attributes
Software Source Selections
Disk & FSLayout
System Identity & Network
IUX Process Control
Recipe for "How to Build a System" Created by UI or by user Can do Conditional Expressions:
(memory > 512Mb){init _hp_pri_swap=512Mb
}else { init _hp_pri_swap=memory*2}
The IUX Config File
ABCHP COMPANY CONFIDENTIAL
SW description of single SD depot or system archive
Default Disk and FS layouts
Local config overrides that apply globally
User named configs
Client-specific configs
Boot control & Networking
Defines a grouping or set of config files
The IUX Index File
ABCHP COMPANY CONFIDENTIAL
System Recovery Tool Now Integrated and on Core Media (Instead of on Support Media)
Tool to Allow Customers To Make Their Own Customized Install Media
Tool to Allow Customers to Make Their Own Customized Recovery Tapes
–see make_recovery presentation Support for Merged SD Depots
New Features for 11.0
ABCHP COMPANY CONFIDENTIAL
How to install and configure Ignite-UX
Chapter 2
ABCHP COMPANY CONFIDENTIAL
The product is available on the external HP Website located at http://www.software.hp.com
Product numbers– B5724AA_APZ (S700)– B5725AA_APZ (S800)
Ignite-UX Software
ABCHP COMPANY CONFIDENTIAL
# B5724AA_APZ 1.09 HP-UX Installation Utilities (Ignite-UX - S700 - 10.20) # B5724AA_APZ.Ignite-UX 1.09 HP-UX System Installation Services B5724AA_APZ.Ignite-UX.BOOT-KERNEL 1.09 Installation Boot Kernel for S700/S800 clients B5724AA_APZ.Ignite-UX.BOOT-SERVICES 1.09 Network Boot Services for System Installations B5724AA_APZ.Ignite-UX.FILE-SRV-10-01 1.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.FILE-SRV-10-10 1.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.FILE-SRV-10-20 1.09 File Archives Used By Clients During HP-UX Install B5724AA_APZ.Ignite-UX.IGNITE 1.09 Graphical Ignite User Interface for Installations B5724AA_APZ.Ignite-UX.IGNT-ENG-A-MAN 1.09 Ignite-UX Manual Pages B5724AA_APZ.Ignite-UX.MGMT-TOOLS 1.09 Tools for Managing Data Files on an Ignition Server B5724AA_APZ.Ignite-UX.OBAM-RUN 1.09 User Interface Libraries Needed for Older Systems
Ignite-UX product structure
ABCHP COMPANY CONFIDENTIAL
HP 9000 Series computer X11 Display server HP-UX version 10.01 or higher; 10.20 is preferred
version to get DHCP support NFS Server Activate tftp service in /etc/inetd.conf 75 Mbytes of disk space for entire product Files are installed under /var/opt/ignite, /opt/ignite and
/etc/opt/ignite Depots created under /var/opt/ignite/depots (can increase
disk space significantly!) Cannot have both NetInstall and Ignite-UX loaded
concurrently Network access to clients Export /var/opt/ignite/clients
Ignite-UX Server Requirements
ABCHP COMPANY CONFIDENTIAL
HP 9000 Series computer with PA 1.1 or later. 32MB Ram Distribution media must be HP-UX 10.01 or greater. Network connectivity to Ignite-UX server. If client is across gateway from server, there must be a boot helper
on the local lan if the client does not have a running OS.
Ignite-UX Minimum Client Requirements
ABCHP COMPANY CONFIDENTIAL
Use swinstall to install softwareswinstall B5724AA_APZ
Control scripts will:ensure NetInstall is not on systemmodify /etc/inetd.conf to enable tftp and instl_bootps servicesadd /opt/ignite/bin to /etc/PATHadd /opt/ignite/share/man to/etc/MANPATHenable rbootd and start it if necessarypreserve existing INSTALLFS data or initialize it on first installation
Software Installation
ABCHP COMPANY CONFIDENTIAL
Execute as root:/opt/ignite/bin/ignite
Select Options->Server Configuration Select Server Options Set fields as follows:
Default Configuration: HP-UX B.10.20 Default
Default Printer: <select a printer>Client Timeouts: 40Run client installation UI on: server
Ignite-UX Configuration: Server Options
ABCHP COMPANY CONFIDENTIAL
During boot, clients need a temporary IP address
Enter a range of IP addresses Permanent IP addresses are
distributed via DHCPCaution if you modify the DHCP class ID or DHCP Addresses are temporaryIf addresses are temporary, they are used only during install phaseEnter a range of IP addresses
Server Customization: IP Address Management
ABCHP COMPANY CONFIDENTIAL
Controls the behavior of Ignite-UX for all clients
Some of these are geared towards manufacturers who use Ignite-UX
IUX Configuration: Session Options
ABCHP COMPANY CONFIDENTIAL
Run /opt/ignite/bin/igniteAt startup, ignite will try to export /var/opt/ignite/clients.NOTE: This is a typical configuration failure situation. Why?
_______________________________________ _______________________________________
Configure the server optionsSelect "Options->Server Configuration"
Configure temporary and permanent IP address for client/target system by selecting "Add booting IP Addresses"
Server Customization
ABCHP COMPANY CONFIDENTIAL
Understanding Config files from tree level.
Chapter 3
ABCHP COMPANY CONFIDENTIAL
/var/opt/ignite/INDEX /opt/ignite/data/Rel_{release}/config /var/opt/ignite/data/Rel_{release}/* /var/opt/ignite/config.local /opt/ignite/boot/INSTALLFS /var/opt/ignite/clients/0x{LLA}/config /var/opt/ignite/saved_cfgs/*
The Config Files
ABCHP COMPANY CONFIDENTIAL
instl_adm (4) man page is the best place to get configuration file syntax descriptions.
>man 4 instl_adm
ABCHP COMPANY CONFIDENTIAL
INDEX file contains a list of valid configurations. Each configuration is made up of one or more config files located in /var/opt/ignite/data/Rel_{release}/*
/var/opt/ignite/INDEX
ABCHP COMPANY CONFIDENTIAL
Default Index file for Ignite-UX# /var/opt/ignite/INDEX: Ignite-UX configurations.
cfg "HP-UX B.10.20 Default" { description "This selection supplies the default system configuration that HP supplies for the B.10.20 release." "/opt/ignite/data/Rel_B.10.20/config" "/var/opt/ignite/config.local"}= TRUE
cfg "HP-UX B.10.10 Default" { description "This selection supplies the default system configuration that HP supplies for the B.10.10 release." "/opt/ignite/data/Rel_B.10.10/config" "/var/opt/ignite/config.local"}
/var/opt/ignite/INDEX
ABCHP COMPANY CONFIDENTIAL
HP supplied set of disk and filesystem layout defaults for each OS release
{release} is the result of the uname -r command. e.g. /opt/ignite/data/Rel_B.10.20/config contains the default
disk layouts for the HP-UX 10.20 release.
/opt/ignite/data/Rel_{release}/config
ABCHP COMPANY CONFIDENTIAL
_hp_disk_layout = { "Whole disk (not LVM) with HFS", "Logical Volume Manager (LVM) with HFS", "Logical Volume Manager (LVM) with VxFS"}_hp_disk_layout == "Whole disk (not LVM) with HFS"{ partitioned_disk { physical_volume disk[_hp_root_disk] fs_partition { usage = HFS size = remaining mount_point = "/" disk[_hp_root_disk].size < 300Mb { # For really small disks, tune down minfree # in order to gain some disk space. minfree = 5 } } }}
A short excerpt from the file
Config file example - Disk Layout /opt/ignite/data/Rel_B.10.20/config
ABCHP COMPANY CONFIDENTIAL
# default (recommended) swap size is 2 X memoryinit _hp_pri_swap = MEMORY * 2
# Put an upper bounds of 512Mb to the default swap size_hp_pri_swap > 512Mb { init _hp_pri_swap = 512Mb }
# Use a 128Mb as the default minimum amount of swap configured on any# system. The real swap space will be reduced down to _hp_min_swap if# there is not enough filesystem space.(_hp_pri_swap < 128Mb) { init _hp_pri_swap = 128Mb }
# Initialize the swap range minimum to what the default_hp_min_swap = _hp_pri_swap
# If the system is limited on resources, then reduce the minimum so# that the OS has a better chance of fitting. The swap size will# sill be set to the recommended value if there is enough disk space.(_hp_min_swap > 192Mb & disk[_hp_root_disk].size < 1800Mb) { _hp_min_swap = 192Mb }(_hp_min_swap > 96Mb & disk[_hp_root_disk].size < 700Mb) { _hp_min_swap = 96Mb }(_hp_min_swap > 68Mb & disk[_hp_root_disk].size < 600Mb) { _hp_min_swap = 68Mb }
Small excerpt of config file
Example of Swap Definitions in /opt/ignite/data/Rel_B.10.20/config
ABCHP COMPANY CONFIDENTIAL
Software description of a single SD depot Describe software available from SD depots are automatically generated via make_config(1m)
One config file per SD depot is created
/var/opt/ignite/data/Rel_{release}/*
ABCHP COMPANY CONFIDENTIAL
software description of an archive. hand-built config file to allow access to non-SD software archives.
archives can either be in tar or cpio format. example files can be found in /opt/ignite/data/examples
/var/opt/ignite/data/Rel_{release}/*
ABCHP COMPANY CONFIDENTIAL
Used to specify defaults which will be applied to every machine installed from a particular server.
Overrides previously specified configurations. e.g. may want to specify the same NIS domain for all
machines.
Creating Generic Information/var/opt/ignite/config.local
ABCHP COMPANY CONFIDENTIAL
config file specific for a client file created by running the GUI to specify the target
machine configuration this file depends on config files listed above can contain specific directives to override definitions in
other config files. e.g. customization of a disk layout beyond the defaults.
/var/opt/ignite/clients/0x{LLA}/config
ABCHP COMPANY CONFIDENTIAL
Named configurations created by saving a configuration via the UI.
Save a configuration for future use. A good way to create a "type" of system that is used
by a particular type of user. i.e. "CAD System"
/var/opt/ignite/saved_cfgs/*
ABCHP COMPANY CONFIDENTIAL
It is recommended that you create and manage your own config files in the /var/opt/ignite directory tree. (Even though you can place them anywhere on your file system.)
/var/opt/ignite/INDEX is the mechanism for grouping individual config files together to create a load configuration.
Working with Config files
ABCHP COMPANY CONFIDENTIAL
Create a config file for each OS Archive, use /opt/ignite/data/examples/core.cfg as a template.
for each archive: cp /opt/ignite/data/examples/core.cfg \ /var/opt/ignite/config/Rel_B.10.20/{system_id}.cfg
The sw_source stanza defines what transfer mechanism the target system will use to transfer the OS archive.
nfs_source = "15.2.72.150:/var/opt/ignite/archives" ftp_source = "anonymous@15.2.72.150:iux" remsh_source = "user@15.2.72.150"
The sw_sel stanza defines the name of the OS archive to be used: archive_path = "{system_id}.gz" e.g. archive_path = "golden_image.gz" The archive path may be a full path for ftp or remsh, but not for NFS
The sw_sel stanza has an impacts section that you must customize for your image. The archive_impact command will automatically generate this information for you:
/opt/ignite/lbin/archive_impact -t -g {system_id}.gz > /tmp/impacts Replace the impacts section of sw_sel stanza with the output from
archive_impact. Add an entry in the INDEX file for this new configuration using manage_index.
Telling Ignite-UX about an Archive
ABCHP COMPANY CONFIDENTIAL
sw_source "core archive" { description = "HP-UX Core Operating System Archives" load_order = 0 source_format = archive source_type="NET"
# The following 2 scripts should be reviewed to see if the # defined defaults are applicable. If you need to modify # them, copy them to /var/opt/ignite/scripts first and change # the paths here. post_load_script = "/opt/ignite/data/scripts/os_arch_post_l" post_config_script = "/opt/ignite/data/scripts/os_arch_post_c"
# If nfs_source is used, be sure to export the source nfs_source = "15.1.54.123:/var/opt/ignite/archives"
# ftp_source and remsh_source is an alternate way to copy # the archive. An example of the ftp syntax: # ftp_source = "anonymous@15.1.54.123:iux" # remsh_source = "user@15.1.54.123" }
Core.cfg example
ABCHP COMPANY CONFIDENTIAL
There are three basic types of software objects in the config file syntax:sw_source
–Specifies a SD depot or an access method to an OS archivesw_category
–Method for grouping sw_sel objects into a logical groupsw_sel
–Typically refers to a single bundle or archive
Software Objects
ABCHP COMPANY CONFIDENTIAL
a category of your choosing pick a label that will help you configure a type of system.
e.g. "CAD-software"
sw_category
ABCHP COMPANY CONFIDENTIAL
Important attributes of sw_source objects–source_type–source_format–sd_server–sd_depot_dir–nfs_source, ftp_source, remsh_source–load_order–pre_load_cmd, post_load_cmd, post_config_cmd–pre_load_script, post_load_script, post_config_script–final_cmd, final_script
sw_source
ABCHP COMPANY CONFIDENTIAL
Important attributes of sw_sel objects– sw_source– archive_path– archive_type– sd_software_list– impacts– mod_kernel– corequisite, exrequisite– load_with_any, load_with_all– pre_load_cmd, post_load_cmd, post_config_cmd– pre_load_script, post_load_script, post_config_script
sw_sel
ABCHP COMPANY CONFIDENTIAL
# /var/opt/ignite/INDEX: Ignite-UX configurations.
cfg "HP-UX B.10.20 Software Depot" { description "Load using the software depot at hpfclc for the B.10.20 release." "/opt/ignite/data/Rel_B.10.20/config" "/var/opt/ignite/config/sw_depot.cfg" "/var/opt/ignite/config.local"}
cfg "HP-UX B.10.20 Default" { description "Load using the GOLDEN IMAGE for the B.10.20 release." "/opt/ignite/data/Rel_B.10.20/config" " /var/opt/ignite/config/core_700_archive.cfg" "/var/opt/ignite/config.local"}
INDEX example changes
ABCHP COMPANY CONFIDENTIAL
When a client is ready for installation, IUX will place the client's config files into the /var/opt/ignite/clients/<lla> directory.
– The client's master configuration file is named "config" The "config" file contains all the relevant configuration information
the client needs to perform an installation.
IUX Creation of Client’s Config
ABCHP COMPANY CONFIDENTIAL
What's happening behind the scenes?
Chapter 4
ABCHP COMPANY CONFIDENTIAL
/opt/ignite/bootINSTALLINSTALLFSboot_liffs_cfg.def
/opt/ignite/dataINSTCMDS
/opt/ignite/data/Rel_B.10.[01,10,20]SYSCMDSconfig
These are the files found on the IUX Server which are used by the client in its initial bootup and installation process.
Client Bootup Process
ABCHP COMPANY CONFIDENTIAL
TargetIUX Server15.2.72.150
boot lan.15.2.72.150 install
pulls over boot_lif via tftpRuns ISL, gets autofile from bootfileautofile pulls "hpux" from bootfile"hpux" pulls INSTALL via tftpSystem jumps to start executing kernelKernel looks for and pulls INSTALLFS via tftpAttempts DHCP request for more permanent IP address (this request wakes up server's bootp).
instl_bootp wakes up- gets a temporary IP address- send udp packet back with IP address and path to tftp bootfile
udp packet
udp packet
Install Boot Process
ABCHP COMPANY CONFIDENTIAL
Target IUX Server15.2.72.150
Pulls INSTCMDS (IUX commands) via tftp.NFS mounts server /var/opt/ignite/clients/ directory.Creates clients/<lla>/ and client_status file on server.
Waits for server.instr file to be created in clients/<lla> directory with the command "start_install".Gets client config files.Based on the OS release to be installed, pulls SYSCMDS from Rel directory via tftp. . . .etcclient will track server.instr file. Server could change request to stop install and reboot!
Server sees new /var/opt/ignite/clients/<lla>
directory, and flags ignite UI of new client. Once config files are generated, created a
server.instr file containing the command "start_install".
Install Boot Process ... continue
ABCHP COMPANY CONFIDENTIAL
The client and server use 2 files to communicate– client_status– server.instr
The server.instr file is how the IUX server communicates with the client. The valid instructions are :
– start_install– cancel_install– halt_system– reboot_system
Ignite and Client Communication
ABCHP COMPANY CONFIDENTIAL
Automatic Installations
Chapter 5
ABCHP COMPANY CONFIDENTIAL
bootsys is an IUX server command which will reboot a target system, and install an IUX operating system.
bootsys provides the mechanism to perform OS installations and configuration from a remote location. You never have to physically touch the target!
Bootsys: The heart of Auto-install
ABCHP COMPANY CONFIDENTIAL
– The "-w" option will cause the target system to reboot, and wait for the next instruction from the ignite interface.
bootsys -w hpfcnjm3.fc.hp.com
– The "-a" option will cause the target system to reboot, and install a new OS based on the IUX default defined.
bootsys -a hpfcnjm3.fc.hp.com
– If neither "-w" nor "-a" are given, then the client will boot using the default mode stored in the INSTALLFS file (modified using instl_adm) using the control_from_server and run_ui keywords.
– The "-v" (verbose) option to bootsys is useful in understanding exactly what bootsys is doing.
– The "-i" options allows the user to specify a specific configuration.
Some bootsys Options
ABCHP COMPANY CONFIDENTIAL
Bootsys modifies the AUTO file and the primary boot device on the target system. Despite being a powerful tool it has potential problems areas:
– HP_UX 10.x has a setboot command to change the primary boot device, but 9.0x systems do not have such a command. Fixing 9.0x system's primary boot device requires interrupting the boot process.
– What happens if you use bootsys to load a new OS on the target, but the target's new root is not the same as the current root disk, AND you plan on keeping the current root disk functional?
The bootsys man page describes how to fix the AUTO file on the target system. It provides a "/tmp/bootsys_prep -u" command to fix the AUTO file.
boot primary isl ISL> hpux /stand/vmunix ( or /hpux for 9.0x systems) /tmp/bootsys prep -u
What bootsys_prep -u really does is to change the AUTO file via the mkboot command (which you can use as an alternative to using bootsys_prep ):
– /etc/mkboot -a "hpux (2/0/1.4.0.0.0.0)/stand/vmunix" /dev/rdsk/<device>– This example assumes a 10.0x system to be booted from scsi device 4.
Bootsys: Cautions
ABCHP COMPANY CONFIDENTIAL
If no user interaction is occurring during an OS install:– bootsys -acontrol_from_server and run_ui are set to false
IUX will choose a config file in this order:– if /var/opt/clients/<LLA>/config exists, use it.– If the bootsys command specified a -i option, then all
config files listed in that cfg clause will be used.Else, it uses whichever cfg clause is the default in the INDEX
file.
What config file will IUX use?
ABCHP COMPANY CONFIDENTIAL
Once you have performed an ignite installation for a system the /var/opt/ignite/clients/*/config file will contain all the specified information.
The config file will contain the following information which could be generic to all systems:
dns_domain="fc.hp.com"dns_nameserver[0] = "15.2.72.2"nis_domain="udl"wait_for_nis_server=FALSEroot_password="rlW2xSrugUvi2"timezone="MST7MDT"ntpdate_server="15.1.48.11"
init sw_sel "Misc_Patches"=TRUEinit sw_sel "B3919DA_AGP"=TRUE
mod_kernel += "maxuprc 100"mod_kernel += "dbc_max_pct 80”
If these parameters are placed in /var/opt/ignite/config.local, they will be picked up by all system installations.
Creating Generic Information
ABCHP COMPANY CONFIDENTIAL
The Golden Image Creating and configuring software sources
Chapter 6
ABCHP COMPANY CONFIDENTIAL
Archive config file
create post_config
scripts
generalize config file
for HWInstall
tune system
create archive
How DO I Make Golden Systems?
ABCHP COMPANY CONFIDENTIAL
Golden Images are also called OS Archives. A Golden Image is a tar/gzip archive of an entire installed and
configured operating system. Administrators will create these images to ease the installation of a
new system. A golden system will vary from site to site, but may contain patches,
kernel parameter settings, common software, and spooler configurations.
A golden system may also be defined for each type of system to be deployed; CAE, MCAD, SWDEV.
Most sites with a large number of workstations will already have a well defined golden system which they would like to distribute.
What’s a Golden Image?
ABCHP COMPANY CONFIDENTIAL
Ignite-UX can install an archive directly or by pulling from a software depot. Using an OS archive is much faster than installing via a software depot.
Depots are easier to manage, but slower. Changing a depot requires that make_config be re-run.
Additional patches or software may be easily added to a depot but not to an existing OS archive.
To add or remove software from an OS archive requires repackaging the entire OS archive.
OS Archives vs. Software Depots
ABCHP COMPANY CONFIDENTIAL
Create a "golden system" containing all common software to the site. Use an OS archive of a golden system to distribute your software. Do not place software that changes, or is not common to all
workstation configurations on the golden system. It is up to the site whether patches are placed on the golden system.
Patches may also be configured as additional software in the "software tab" of ignite.
Manage different archives for ME, EE, and SW seats.
Recommended Strategy
ABCHP COMPANY CONFIDENTIAL
Load OS and all common software on a system. Perform all local customizations possible
a file system layoutb printersc special configurations
IUX will rebuild kernel and load necessary drivers automatically. As part of the OS installation process, IUX will build the correct kernel for the workstation model being installed.
Make sure system is quiet, e.g. set to single user mode. Use make_sys_image to create the OS archive:
a copy /opt/ignite/data/scripts/make_sys_image to /tmp on golden system.b Run make_sys_image and have it place the resulting archive on the server. Must
have .rhosts set up on server. /tmp/make_sys_image -d /var/opt/ignite/archives/Rel_B.10.20 -s 15.2.72.150 -n
10.20core
Creating an OS Archive for IUX
ABCHP COMPANY CONFIDENTIAL
Customizing your configurations– Include Additional Software– Tweak Kernel Parameters– Include Patches
Chapter 7
ABCHP COMPANY CONFIDENTIAL
The software tab of ignite allows for software selections to be shown and selectively loaded onto the target system.
Addition software includes: Any bundled software in an SD depot. Any non-SD packaged software, a tar or cpio archive.
Set this up like an OS archive with a load order of 6 or more. Installation of additional software may be set-up as conditional or
automatic
Additional Software in Configuration
ABCHP COMPANY CONFIDENTIAL
Use normal SD tools to create a software depot– swcopy, swreg, . . .
IUX has tools to create configuration file for software depots:– /opt/ignite/bin/make_config -c <name of config file> -a <type of config> \
-s <source depot> – make_config -c /var/opt/ignite/config/app_bundle.cfg -a 700
-s hpfclc:/release/S700_10.20– make_config works only at the depot level not on packages.
Use manage_index to put config file in INDEX file– manage_index -a -f /var/opt/ignite/config/app_bundle.cfg -r B.10.20
Creating an OS Software Depot
ABCHP COMPANY CONFIDENTIAL
Software bundles can be configured as conditional or automatic:– Automatic:
In the sw_sel stanza of the application configuration file (/var/opt/ignite/config/app_bundle.cfg) add the following line:
load_with_any = "golden image" The name "golden image" is the name used in the sw_sel stanza in an OS archive
configuration file /var/opt/ignite/config/core_700_archive.cfg.
– Conditional: Set up a boolean expression:(graphics[0].id == 0x2FC1066B){init sw_sel "B6196AA_APZ"=TRUE}
Conditional or Automatic Loading
ABCHP COMPANY CONFIDENTIAL
You can define system kernel parameters in much the same way as you define additional software.
Example config file (/var/opt/ignite/config/kernel_mods.cfg):
HARDWARE_MODEL ~ "9000/7.*" {
sw_sel "Basic_Kernel_Mods" { description = "Basic Kernel parameters only" sw_source = "cmds" sw_category = "HPUXAdditions" <---- This could be any name you choose mod_kernel += "nproc (20+12*MAXUSERS)" mod_kernel += "maxuprc 127" load_with_any = "golden image" <---- Cannot be unselected in ignite } sw_sel "Advanced_Kernel_Mods" { description = "Advanced Kernel parameters" sw_source = "cmds" sw_category = "HPUXAdditions" mod_kernel += "maxdsiz 0x0A000000" mod_kernel += "maxtsiz 0x06000000" } = TRUE <---- The "= TRUE" will cause these to } # end of hardware-specific section be selected by default.
Defining kernel parameters in config
ABCHP COMPANY CONFIDENTIAL
It is easy to change kernel parameters in much the same way as it is to load software.
sw_sel "Compute Server" { description = "Compute Server Configuration" sw_category = "SpecialConfigs" sw_source = "special configs" mod_kernel += "fs_async 1" mod_kernel += "maxdsiz 0X3BC00000" mod_kernel += "maxfiles 2048" mod_kernel += "shmmax 0x40000000"}
Modifying kernel parameters
ABCHP COMPANY CONFIDENTIAL
You can use the same mechanism used to load additional software to load patches. ( Ignite only understands bundles, and HP-UX patches are products.)
Ignite-UX ships a tool called make_bundles which can take all the desired patches and store them into a single patch-bundle.
The one problem with this approach is whenever a new patch needs to be added to the bundle, make_bundle, and make_config need to be re-run. These are fairly quick steps.
Look at the Appendix B of Ignite-UX Startup Guide... (Appendix B) for the steps needed to manage HP-UX patches .........
Managing Patches
ABCHP COMPANY CONFIDENTIAL
Adding Post Installation Scripts
Chapter 8
ABCHP COMPANY CONFIDENTIAL
Post-install scripts are used to do things that Ignite-UX cannot presently do:
– NFS configuration– Mounting additional disks– Configuring spoolers– Loading additional application software not stored in an SD depot– HW customizations not supplied in archive– Copy user data to target
Two scripts are supplied by Ignite-UX to handle OS archive loads:– /opt/ignite/data/scripts/os_arch_post_c (configure)– /opt/ignite/data/scripts/os_arch_post_l (load)
Using Post-Installation Scripts
ABCHP COMPANY CONFIDENTIAL
Post Installation scripts can be defined in any configuration file.– in sw_source– in sw_sel– in the "scripts" section of the INDEX file– see instl_adm (4) for more detail
Use the post_config_script parameter to define a script– post_install_script += "/var/opt/ignite/scripts/install_netscape"– If multiple scripts are defined, remember to use the "+=" syntax
The target system will have the ability to access the IUX server via rcp, so the post installation script has the ability to pull over additional files.
Put user scripts in /var/opt/ignite/scripts Appendix D of the Ignite-UX Startup Guide gives more details on
adding post-installation scripts.
Adding Post-Installation Scripts
ABCHP COMPANY CONFIDENTIAL
If the administration task you are performing is one which could be done via SAM, you can cut-paste from SAM's logfile into your script file:
– Invoke SAM– Perform Options->View Sam Log– Change "Message Level" to "Commands Only"– Perform your task (i.e. add a printer)– Exit Sam or save logfile (you cannot cut and paste from SAM log window)– Cut commands from SAM log file and paste into your script
Example from SAM logfile for configuration of a remote printer, and starting the lp print scheduler.
lpmgr -a -xlocalname=tsslj, default=y,fence=0,rc=n, is_bsd=n,remname=tsslj, remsys=hpfcmgw.fc.hp.com, \remcancel=rcmodel, remstatus=rsmodel
/usr/sbin/lpadmin -ptsslj -ormhpfcmgw.fc.hp.com -orptsslj -mrmodel -v/dev/null -ocmrcmodel -osmrsmodel /usr/sbin/lpadmin -dtsslj /usr/sbin/accept tsslj /usr/bin/enable tsslj lpsched -v
Hints on Creating Scripts
ABCHP COMPANY CONFIDENTIAL
A list of optional scripts may also be defined in the INDEX file.scripts { "script-file-path-name-1" "script-file-path-name-2" }
These scripts will show up in the advanced tab, and will be selectable.
Make sure the directory where the script resides is available to tftp.
Scripts defined in the INDEX file
ABCHP COMPANY CONFIDENTIAL
Setting Install Parameters Dynamically
Chapter 9
ABCHP COMPANY CONFIDENTIAL
At install time, based on existing system parameters (e.g. disk space), a system parameter on the target system can be set (e.g. swap size)
As an example, we'll set the primary swap size of the target system root disk dynamically at install time based on the size of the disk, and on the size of the target system RAM. The algorithm will set swap to 125 MB if the disk is large (> 500MB) and if the amount of system RAM > 64MB. If we have a small disk we'll make the swap very small to maximize the amount of space available for HP-UX system files.
You could add the following lines to the end of the file /var/opt/ignite/config/core_700_archive_cfg or to /var/opt/ignite/config.local if you would like this to be the default for all configurations.
# default to very minimal swap of 25MB unless the disk is larger than 500 MB # and we have more than 64MB ram (disk[_hp_root_disk].size > 500MB & memory > 64MB) { init _hp_pri_swap=125MB } else { init _hp_pri_swap=25MB }
Dynamic Install Parameters
ABCHP COMPANY CONFIDENTIAL
In this example, we'll force the load of a patch bundle if we determine the target machine matches the regular expression "71*", such as a 710, 712 or 715: # check for H/W model 71x # and add the Misc_Patches bundle if true (hardware_model ~ "9000/71*") { init "Misc_Patches" = true }
This example will run a previously created post install script and increase a tunable kernel parameter if we determine our target machine is a Model 755. If not, it sets a default value for the kernel parameter: HARDWARE_MODEL == "9000/755" { post_config_script += "/var/opt/ignite/scripts/755special"
mod_kernel += "maxuprc 300" } else { mod_kernel += "maxuprc 100" }
Dynamic Install Parameters ... cont.
ABCHP COMPANY CONFIDENTIAL
Igniting systems across subnets
Chapter 10
ABCHP COMPANY CONFIDENTIAL
HP-UX can not cold boot across a gateway. Therefore, Ignite-UX does not have that ability.
In order to manage a network from a single point, to ignite a system without a viable OS across a gateway, it is necessary to set up a boot helper:
– The helper will provide the initial bootfile, INSTALL and INSTALLFS– Once the target is booted and communicating on the network, it will be able to
communicate with a ignite server anywhere on the network.– Its only requirement is to be able to tftp, and NFS mount the server system
across the gateways.If the target is already running HP-UX 9.x or 10.x, it will not need a boot helper. IUX
can install a new OS via the bootsys interface. The boot helper is only needed for the initial system bootup.
Chapter 6 of the Ignite-UX Startup Guide (Appendix B) describes how to set up a boot helper.
Igniting your Network
ABCHP COMPANY CONFIDENTIAL
The Ignite-UX product contains the software to set up and configure a boot helper. To set up a boot helper:
Chose one system on each subnet to be the helper Load Ignite-UX's minimum core onto the boot helper system
e.g. swinstall -s 15.2.72.150:/var/opt/ignite/sw_depot Ignite-UX.MinimumRuntime
Change the server's INSTALLFS to point to the correct Ignite server e.g. /opt/ignite/bin/instl_adm -t 15.2.72.150 -g <gateway>
Verify the contents of INSTALLFS using "instl_adm -d". Add temporary boot IP address to /etc/opt/ignite/instl_boottab
boot helperboot helper boot helperIUX Server
System A
Setting up a boot helper
ABCHP COMPANY CONFIDENTIAL
Hints on trouble shooting Other things that didn't
have a home
Additional Information
ABCHP COMPANY CONFIDENTIAL
Tools for managing bits on the server– add_release– remove_release– make_config– make_depots– make_bundles– manage_index
Tools for managing the install server– setup_server– instl_adm
Ignite-UX Toolset Includes:
ABCHP COMPANY CONFIDENTIAL
Tools for system cloning– make_sys_image– bootsys– save_config
Tools for media creation– make_medialif
Tools for system inventory– print_manifest
Special daemon– instl_bootd
Ignite-UX Toolset (cont.)
ABCHP COMPANY CONFIDENTIAL
There is one in compatible syntax difference. (now supports multiple lan cards.)
cold Install: ip_addr="15.88.26.55"Ignite: ip_addr[0]="15.88.26.55"
Many custom Cold Install config files used post-config scripts to load additional software. This can be done directly with Ignite-UX.
It is probably better to look over any existing config files, read and understand instl_adm(4), toss the files away, and rewrite them to take advantage of the additional capabilities of Ignite-UX.
Migrating existing Cold Install config files to Ignite config files
ABCHP COMPANY CONFIDENTIAL
review rodean’s advanced topics #1 & #2 FDDI-only environments
– since FDDI systems cannot boot over the LAN, you must use bootsys to initiate installation
– FDDI drivers are currently not included in the install kernel drivers (INSTALL) - causes a problem.
Series 800 Network Installs– Only D- and K- class systems without viable OS's can be booted and installed over the
network. Others need to have a boot disk with the install kernel(INSTALL) and install file system (INSTALLFS). The AUTO file must select the install kernel instead of the normal /stand/vmunix. The install file system should point to the Ignite-UX server.
Server Management– There are no supplied tools to verify the health of an IUX server. Some problems:
IP address management (temporary and final) config and INDEX file management automated boot helper setup
Misc.
ABCHP COMPANY CONFIDENTIAL
Known problems are detailed in the release notes
– Wrong primary swap partition– Partial set_parms data– Timezone info in /etc/TIMEZONE but not timezone kernel parameter– No-display option– UI cannot specify kernel parameters– DNS server must be specified by IP address, not hostname– Patch for pax command necessary– If archive is not available, IUX does not detect this until very late - error
message is not intuitive.
Troubleshooting Ignite-UX
ABCHP COMPANY CONFIDENTIAL
Log files– Most commands use a log file which is found in
/var/opt/ignite/logs/<command> Software doesn't load
– Some bundles have defective control scripts which fail to load on IUX. Workarounds are given in the release notes.
B3898AA_APZ J2220A_APZ J2221A_APZ J2222A_APZ J2223A_APZ
Troubleshooting Ignite-UX (cont)
ABCHP COMPANY CONFIDENTIAL
DHCP– Check files: /etc/dhcptab /var/adm/syslog/syslog.log /etc/inetd.conf
/etc/dhcpdb– Run the command instl_adm -d. Check that dhcp_class_id is set, and that it
matches /etc/dhcptab.– Install the bootpd patch. Once this is installed, the -G option can be added to
the dhcp_class_id keyword which causes the client side to ignore responses from servers that do not have the correct class id. The Microsoft server does not appear to do this.
– Run a recovery shell on the client and check the file /etc/dhcpclient.data. The third line will have the name of the DHCP server
Troubleshooting Ignite-UX (cont)
ABCHP COMPANY CONFIDENTIAL
Client won't boot– Check the files: /var/adm/syslog/syslog.log /etc/opt/ignite/instl_boottab
/etc/inetd.conf– Make sure you are using the right syntax:
boot lan.<IP> install (newer systems) boot lan.<lanic id> (older systems) Older systems may take a long time or require several search or boot
attempts.– If client was originally a diskless client of the Ignite server, the entry for the
client must be removed from the /etc/bootptab or changed to bf=/opt/ignite/boot/boot_lif.
– Make sure you have tftp access to /var/opt/ignite and /opt/ignite (look in /etc/inetd.conf)
Troubleshooting Ignite-UX (cont)
ABCHP COMPANY CONFIDENTIAL
Software not listed in GUI– Make sure you have run make_config & manage_index on all software depots
you want to access.– Check that /var/opt/ignite/INDEX has all the config files for the configuration
you are using. You may have to run make_config.– Note that language environments are not listed. They are set on the Basic
screen. Network info not permanent
– Run the command instl_adm -d. Check that is_net_info_temporary is set to FALSE.
– If you use the GUI and went to the system tab, was the button for network information set as expected?
Troubleshooting Ignite-UX (cont)
ABCHP COMPANY CONFIDENTIAL
Debugging tricks– If system hangs while looking for I/O devices, turn on debug:
isl> hpux -i4 /stand/install or isl> hpux -i4 /boot/install
– can set a debug option later in the install process to check on disk configuration process, etc.
in config file: env_vars = "INST_DEBUG = 4"– If getting a syntax error in a config file, look for the error a line or two above
where the syntax error is flagged
Troubleshooting Ignite-UX (cont)
ABCHP COMPANY CONFIDENTIAL
Ignite-UX Startup Guide for System Administrators Installing and Updating HP-UX 10.x HP9000 Computers Ignite-UX manual entries (/opt/ignite/share/man*.Z) Ignite-UX documentation (/opt/ignite/share/docs) Ignite-UX Cold Installation (Interworks paper)
–Available via http://hpfcdn.fc.hp.com/IUX.html
Ignite-UX FAQ available by email (iux_faq@hpfcdn.fc.hp.com) Effective 7/14, there will be KDB documentation
–In the extended search screen, put Ignite-UX in the TEXT field and put UNX1030* in the ID/DATE field.
Check out the Ignite-UX page accessed from http://www.software.hp.com
Ignite-UX Reference Materials
ABCHP COMPANY CONFIDENTIAL
Using swinstall, install Ignite-UX on your server.– Use ______________ as your install depot
Goto Server configuration options, and configure the server.– Use Initial IP Addresses of ________________ to ________________– Use DHCP Addresses of ________________ to ________________
Does your configuration work?– Using your second system, reboot it, and interrupt the boot sequence.– At the boot prompt, type "search lan" or "search lan install"
This will search the network for available network boot servers.– Perform a network boot of this system (client/target) from the server.
boot lan.15.2.72.150 install <----- Example ISL boot sequence.– NOTE: The boot sequence is dependent on the bootrom. If there is only 1 install server on the network (which is
not the case in this class environment) then you would only need to type "boot lan". See page 5-3 and 5-4 of the Installing manual (Appendix E).
Within 2-4 minutes, an icon for your target system should appear in the GUI.– Hightlight the icon, and perform a "New->Install".– Step through the menu tabs, but DO NOT PERFORM A "Go!".– In the "Sytem" tab, where does the Hostname, and IP Address come from?
_________________________________________________________– "Cancel" the install.
Lab 1: Install and Configure Ignite-UX
ABCHP COMPANY CONFIDENTIAL
For this lab you will follow the instructions documented in the "Ignite-UX Startup Guide for System Administrators" (Appendix B).
Using the "golden image" file on ________, named _________ copy the golden image onto your system, and place it in the /var/opt/ignite/archives/Rel_B.10.20 directory on your IUX server (you may need to create this directory).
Go to Chapter 2 of the Guide, (Appendix B) and follow steps 2 through 5.
Note: Step 3 introduces you to the bootsys command. If you have a running system, you may use this command. If you do not have a system with a viable version of HP-UX, you will need to use the "boot lan install" method.
Lab 2: Building a config file for a “golden image”
ABCHP COMPANY CONFIDENTIAL
When Ignite-UX is installed, the post-configuration process modifies INSTALLFS to match the server configuration.
type "/opt/ignite/bin/instl_adm -d" Using the instl_adm(1M) and instl_adm(4) man pages, determine what each of the fields
mean:server _________________________________________________________netmask _______________________________________________________route_gateway __________________________________________________route_destination _______________________________________________# _____________________________________________________________run_ui ________________________________________________________control_from_server _____________________________________________
Again, using the man pages, what would the following INSTALLFS changes do:
halt_when_done=true _____________________________________________clean_all_disks=true _____________________________________________
These are parameters set by default on distributors' versions of Ignite-UX.Why? __________________________________________________________
Which ignite Server Session Options would perform an instl_adm modifying INSTALLFS? ______________________________________________________
Lab 3: Understanding INSTALLFS
ABCHP COMPANY CONFIDENTIAL
Using the class notes and Ignite-UX Startup Guide: Create a patch depot in /var/opt/ignite/Patches from the patches
available on ________ Using the software depot on_______ for application software,
add "additional software" to be selected in the software tab. Modify the installation kernel parameters to set maxdsiz to
500MB and maxuprc to 120.
Lab 4: Customizing your installation
ABCHP COMPANY CONFIDENTIAL
Appendix A: Complete Core.cfg example