HP Ignite-UX manuals

271 pages4.42 Mb

213 pages1.22 Mb

1Ignite-UXCustom Configuration Files
6Abstract
Introduction
7Typographic Conventions
8HP-UX11i release names and release identifiers
9Configuration files and INDEX files
- 10The CINDEX file
- CINDEX
  - CINDEX
  - make_net_recovery
  - file is created and managed file is the same as the INDEX
- The per-clientconfiguration file
  - var/opt/ignite/clients
  - MAC
- 11The global config.local file
  - /var/opt/ignite/config.local
- The recovery config.local file
  - For make_net_recovery, if the file
  - For
  - if the file
  - exists on the
  - Ignite-UX
  - if the file
- Order of precedence of configuration files
  - 1.The per-clientconfiguration file (/var/opt/ignite/clients/<MAC>/config) —
  - 08,12:45 Recovery Archive
  - 2.The per-client CINDEX file (/var/opt/ignite/clients/<MAC>/CINDEX) —
  - per-client
  - file
  - 3.The global INDEX file (/var/opt/ignite/INDEX)—
  - The global
- 12Testing the order of precedence
  - It is possible to test the order of precedence using the instl_dbg command:
  - 2003-10-08,12:45
  - Recovery Archive
  - 10-08,12:41Recovery Archive) instead:
  - ) instead:
  - The instl_dbg command is covered in more detail in a later section
- 13What is in a configuration (cfg) clause
  - The cfg clause needs the following information:
  - 1.A name (for example, HP-UXB.11.11 Default)
  - 2.A description (see the description keyword)
  - 3.A list of one or more configuration files referenced by this cfg clause
  - 4.One or more configuration files that define software that may be installed4
- 14The make_net_recovery configuration files
- make_net_recovery
  - The three configuration files are as follows:
  - 1.system_cfg –
  - save_config
  - 2.control_cfg –
  - 3.archive_cfg –
  - Basic
- The make_tape_recovery configuration files
- make_tape_recovery
  - make_tape_recovery
15Using the manage_index command
- 16Adding a configuration file to a clause or "release
  - B.11.23
  - One of the configuration files in a
  - /var/opt/ignite/data/Rel
  - /opt/ignite/data/Rel
  - The configuration file starts with the path
  - /opt/ignite/data/Rel_B.11.11/config
  - /var/tmp/config_a
- 17Adding scripts to the INDEX file
  - scripts
  - Advanced
- 18Removing cfg clauses from an INDEX file
  - "testing two
- 19Setting the default cfg clause in an INDEX file
- 20Listing the names of cfg clauses in an INDEX file
  - For example:
- 21Listing the name of the default cfg clause in an INDEX file
- Renaming a cfg clause in an INDEX file
  - The following example swaps two cfg clauses:
- 22Creating a new cfg clause from an existing clause
  - manage_index
- Removing a configuration file from a cfg clause
  - “testing”
  - config_c
  - "testing
  - /var/tmp/config_c
- 23Removing a script from an INDEX file
  - The following example adds a script and then removes it:
- 24List the names of all configuration files in a cfg clause
25Using the make_bundles command
- 26The make_bundles first form
- 27The examples in this section operate on the following depot:
- The following example bundles all the patches:
- 28======= 08/30/07 16:25:13 EST END swpackage SESSION
- PHCO_33976
- 29Now the depot lists two revisions of the bundle:
- PB_Sept_2007
- 30Now we can create the PSF file
- You can then package the bundle manually:
- 31The make_bundles second form
- 33The make_bundles third form
- 34[-l file| product/fileset...] depot_path
- Next, you create another PSF but this time with the extra pax patch PHCO_33967:
35Using the instl_dbg command
- 36Combining instl_dbg and itool
- Running instl_dbg
  - /var/opt/ignite/clients/<MAC
  - 37amount shy (KB)
- 41Other instl_dbg options
- instl_dbg
  - –vvv
  - Refer to instl_dbg(1M) for more information on other options available
- The hw.info and host.info files
  - Both the hw.info and host.info files can be created in either of two ways:
  - When you add a new client to the
  - add_new_client
  - When a new client boots from the
  - io.info
- Creating both files
  - 42<MAC
  - never
43Miscellaneous configuration tips
Analyzing the HP-UXdefault B.11.11 cfg clause
- 44must
- As of Ignite-UXC.6.0.x, the release keyword is checked against the value of the
- _hp_ikernel_os_release
- Table
- 45<variable> visible_if false
- Additional
- is_hppa
- unifdef
- unifdef
- File System:
- 46init _hp_disk_layout
- "_hp_disk_layout="…
- _hp_disk_layout
- _hp_disk_root
- _hp_primary_path
- 48(<variable>={ value1, value2, …
- hp_pri_swap
- Root Swap (MB)
- [_hp_root_disk
- 49enum
- YES
- 50Now you have another effects relationship, this time between a new variable
- and
- . The variable
- is meant to be an integer so when doing the effects relationship you add zero
- ) to
- num_disks
- 51/usr
- /var
- _hp_disk_layouts
- _hp_disk_config
- ∙A physical_volume definition
- definition
- ∙An fs_partition definition
- ∙A swap_partition definition
- Go
- swap_partition
- 52minfree
- _hp_group_name
- 53A volume group definition must have the following things in it:
- ∙volume group attributes
- one or more
- physical_volume
- ∙one or more (usually more) logical_volume definitions
- *=<index
- max_physical_extents
- vgcreate
- 54physical_extent_size
- 55vgdisk
- 56bad_block
- _relocate
- 59stripes
- _hp_FS_stripe_size
- /opt
- /var/adm/crash
- 60/tmp
- /export
- 61/home
- 62autoboot
- setboot
- _hp_force_autoboot
- 63disable_dhcp=true]
- The last part of configuration accomplishes several things:
- 1.Sets the os_release attribute for the swinstall command line
64Analyzing the HP-UXdefault B.11.31 cfg clause
- 65Please note the following text from the Ignite-UXC.7.0 release notes:
- 66_hp_ikernel_os_release
- B.11.31 does not support 9000/7xx workstation systems
- B.11.31 requires at least 1GB of system memory
- 67_hp_efi_partition_size
- enum
- _hp_efi_partition
- 68is_ia64
- File System
- 72[_hp_root_disk].model
- 73FALSE
- 74_hp_min_swap
- 76A volume group definition must have the following:
- *=<index
- max_physical_extents
- 78bad_block _relocate
- 79"Create separate volumes (/usr, /var, ...)
- Logical Volume Manager (LVM) with HFS
- 81Create /export volume
- TRUE
85Special variables
- _hp_locale
- 86_hp_cfg_detail_level
- 87_hp_pri_swap
- _hp_min_swap
- 88_hp_disk_layout
  - 891.Enter:
  - Change the type of disk layout by selecting the
  - Quit the
  - Edit
  - and remove
  - from the front of the
  - variable
  - 5.Save the file
  - Rerun the
- 90_hp_default_cur_lan_dev
- _hp_default_final_lan_dev
- 91_hp_keyboard
- 92_hp_root_disk
- _hp_boot_dev_path
- 93_hp_primary_path
- _hp_primary_partition_size
- _hp_efi_partition_size
- 94_hp_service_partition_size
- _hp_root_grp_disks
- _hp_root_grp_striped
- 95_hp_addnl_fs_free_pct
- _hp_ignore_sw_impact
  - 96tmp/a
- 97_hp_custom_sys
- 98_hp_lanadmin_args
- 99_hp_nfs_mount_opts
- _hp_nfs_mount_retries
- 100_hp_tftp_cmds
- _hp_hide_other_disks
- _hp_saved_detail_level
- 101_hp_os_bitness
- _hp_force_autoboot
- 102_hp_ikernel_os_release
- _hp_current_client_release
- _HP_CLONING
- 103_hp_console_verbosity
- _hp_patch_save_files
- 104_hp_umask
- _hp_ht_enable
- _hp_debug_level
105Configuration for software to be installed
- 10632-bitsystems):
- b_PHSS_28764
- 107T1335AC
- corequisite
- autoselect_patches=true
- 109/var/opt/ignite/data/Rel_B.11.11/vpars_A.02.03.02.cfg
- architecture
- vendor
- revision number
- version number
- 110Core operating system depot configuration
  - 112sw_sel "OE90BaseOS64
  - "English
  - 113"9000/8
  - 9000/8
  - (0)
  - or more of that character. The regular expression
  - "9000/8
  - "ia64 .* server
  - "ia64.*server
  - sw_sel "English
  - If you have a workstation, initialize the sw_sel clause, "Global", to be TRUE
  - Otherwise the sw_sel "English" is set to TRUE
  - 115Software
  - HPUXBaseOS
  - ps2
  - has_ps2
  - Not Applicable
  - has_usb
  - Keyboards…
- 116Impacts statements
- 118Overstated SD impacts
- Categories and other Ignite-UXsoftware attributes
  - 119cat
  - The following is what is special about these categories:
  - OpEnvironments
  - Environments:
  - HPUXBase32
  - Languages
  - LanguagesUI
  - Swedish
  - CDE-Swedish
  - load_with_any
  - UserLicenses
- 120Looking at a network recovery sw_source and sw_sel
- 122Using a sw_sel to run commands instead of installing software
- 123Using a sw_sel to apply kernel parameters
- 124KernelConfig
- 125set_kernel
- exrequisites
- sw_sel "B9789AA, r=1.3.1.09.08
- sw_sel "Kernel Config for Java
- 126"Kernel Config for Servers
- "Kernel Config for Workstations
- mod_kernel
- rm_kernel
- tunable
- state
- static
- auto
- loaded
- best
- kcmodule
- So to tune maxdsiz at HP-UXB.11.11, you would need to set it as follows:
- At HP-UXB.11.23, you should use:
- 127Forcing software (sw_sel) clauses to be installed
- Automating dependencies in software
- 128See "Using a sw_sel to apply kernel parameters" for exrequisite examples
- fnmatch
- (3)
129Configuration for volume and disk groups
- 130Overview
131Configuration examples
- 132The test on
- to the variable set
- is only evaluated once. If
- Next is the definition of the disk layout Custom configuration for Product XYZ:
- 133_my_volume_group
- 134Product XYZ – 4GL
- The last volumes are defined as follows:
- usage = LVM
- usage = VXVM
- 136Example Two (selection of disk layout based on hardware)
  - 137Custom configuration rp8400 w/18GB disks
  - warning
- 138Example Three (be careful what you ask for, you just might get it)
  - disk[_hp_root_disk].size
  - During installation those errors would look like:
- 139Part A (custom configuration in installation file system)
- 140Part B (Installation file system custom network config)
- 141Part A (restricting the values that a variable can take using an enum)
- 142Part B (looking at the same thing when we don’t have an enum)
- ∙-cwhich needs to be able to take any specified value (a user name)
- We can put together a command line as follows:
- The variable _my_command_line could be used in the following way:
- or be placed into the environment for when a script is ran later:
- 143Example Seven (regular expression matching)
  - 144You can give a character class in the regular expression, for example
  - Do not use the construct
  - 145zero
  - 146– E
  - Another example:
  - Testing this with grep you can see that this does work:
  - 147would match:
  - 1.Something that starts with “ab“
  - 2.Something that contains “cd“
148Configuration parameters in the installation file system
- 149dhcp_server
- dhcp_server = "10.0.0.53
- dhcp_server[0/0/0] = "10.0.0.54
- dhcp_misc_opts
- dhcp_misc_opts
- "-l
- dhcp_misc_opts[0/0/0]
- /usr/lbin/dhcpclient
- disable_dhcp
- 150Problems that can be solved with _hp_lanadmin_args
- _hp_lanadmin_args
  - only
- 151Control
- 152Environment variables
  - env_vars
  - tztab
  - INST_NET_RESPONSE_TIMEOUT—
  - If this value is set to >0 the following message appears:
  - If neither Enter nor Return is selected within 10 seconds, the system reboots
  - INST_ALLOW_WARNINGS
153Managing configurations with unifdef
- 154The unifdef command recognizes the following C preprocessor directives:
- With these directives, you can change the configuration file as follows:
155Coping with auto_adm and boot changes in HP-UXB.11.23
- 156CONF data
- 157auto_conf
- CONF
- default
- message
- label
- bootcmd
- boot
- image
- hpux
- 158ISL data
- Creating new files
- 159Adding new menu entries to a file
- 160Using an "append" file
- Updating a menu entry in a file
- 161Deleting a menu entry from a file
- 162Changing the default menu choice
- Changing the timeout
- Updating the prompt message
- Into and out of an LIF file
163Installation configurations using Software Distributor depots
- How to configure
- instl_bootd
- instl_bootd
- How to setup depots up remote to the
- How to use this process with versions earlier than the C.6.0
- 164Getting started
  - Successful System Cloning using Ignite- UX
- Creating the core operating system depot
  - make_depots -rB.11.11 -s /dev/dsk/c0t1d0
  - If the command is successful, no output is displayed by make_depots
  - 165/var/opt/ignite/depots/Rel_B.11.11/core
  - /var/opt/ignite/logs/make_depots
- 166Operating Environments containing multiple CDs or DVDs
  - Perform the following steps to copy 11i v2 from multiple DVDs:
  - 1.Insert the first DVD from the March 2006 11.23 OE
  - 2.Run the following command:
  - 3.Remove the first DVD from the DVD drive
  - 4.Insert the second DVD from the March 2006 11.23 OE
  - 5.Run the following command:
  - 6.Remove the second DVD
  - 2005 11i v1 OE media on CD to a depot follows:
  - 1.Insert the first CD from the September 2005 11.11 OE
  - 3.Remove the first CD
  - 4.Insert the second CD from the September 2005 11.11 OE
- 167Using the Ignite-UXGUI
- 1682.Select Run Tutorial/Server Setup… from the Actions menu
- Server Setup
- 169The third step
- Set up Software
- Next
- Copy CD/DVD
- Use CD/DVD
- 1706.Insert the media as requested and click OK
- 7.Select the correct CD or DVD device from the drop-downbutton then click OK
- Review the information you have entered to be sure it is correct and then click
- 172Cancel
- 173The pitfalls of using multiple media
- 174This creates the configuration file that describes the depot in
- and it is named
- . However, it does not update
- so that you can create your own custom
- An alternative to this is to use the following command:
- For example, if you run the following command:
- If you then run the following command:
- core_cfg
- 175Creating a minimalist cfg clause for installation
  - When complete you have a new cfg clause in the INDEX file:
- 176Creating the application depot
- Creating a configuration for the application depot
- 177An example problem
- 178Follow on consequences
- 179Package an application in SD format
- 180Define an application in a non-SDformat
- 181Base OS
- MyApp
- 182Required
- Additional system hardware tests are explained in the following section
- 183Using noncore.cfg to define applications
- noncore.cfg
  - /opt/ignite/data/examples/noncore.cfg
  - noncore.cfg
  - 1849000
  - 185The sw_sel clauses are self-explanatory.The important parts are:
  - ∙The src, which defines where the software is located
  - The archive type, which defines that it is a gzipped
  - ∙The archive name or path of the archive
  - The impacts statements that enable
  - archive_path
- 186SD and archive bitness comparison
  - wlist
  - fileset
  - name
  - HP-UX:*64
  - 187Adding the non-SDapplication configuration file to the INDEX file
- Setting up the depot
- Packaging the patches into a bundle
- 188Generating a configuration
- 189Customizing configuration
  - In the current INDEX file, you have the following cfg clause:
191Performance considerations for SD-UXbased installs
- 192Tuning SD-UXfor concurrent access
  - /usr/lib/sw/sys.defaults
  - swagentd.rpc_max_calls=n
  - rpc_max_calls
  - # swagentd –r –xrpc_max_calls=n
  - and other
  - SD-UX
  - swcopy
  - to be
- Issues to consider related to the HP-UXrevision
  - rpc_max_calls
  - nproc
  - swagent
  - swagent;
- 193Memory and the buffer cache
- 194Network Bandwidth
195Installation configurations using golden images
- 196/opt/ignite/data/Rel_B.xx.yy/config
- core11.cfg
- archive
- 197post_load_script
- os_arch_post_l
- /var/opt/ignite/scripts
- post_load|config_scripts
- /opt/ignite/data/scripts
- 198golden image - 32 bit OS
- !can_run_64bit
- can_run_64bit
- 199English
- 200The format of a entry in the locale list is:
- <locale
- "locale
- -a
- ja_JP.SJIS
- "ja_JP.SJIS:Japanese_SJIS
- 201Instances that may require modifying os_arch_post_l
- os_arch_post_l
  - /usr/newconfig
  - merge_file
  - merge_file /etc/hosts
  - save_file
  - In summary you can use:
- 202Creating a golden image
  - make_sys_image
  - make_sys_image
- Final words about golden image installations
  - config.local
203Understanding what is_net_info_temporary does
204Understanding how VxFS file system versions are set
205How do I…
- 206How do I recognize if a disk exists or not from within a configuration file
  - You can change the sense of the test by adding a logical not operator (!):
  - For a more complete test, you could combine the previous examples as follows:
  - not
- 207How do I create the CD equivalent of a tape created by make_boot_tape
- make_boot_tape
  - This media can be used for several practical purposes:
  - For use with tape recovery when you need to perform
  - 208Create a LIF. If you are using Ignite-UXversions before C.6.0, enter:
  - If you are using Ignite-UXversions C.6.0 and later, enter:
  - To verify the lif contents, use the following commands:
  - 209not
  - IINSTALLFS
  - output
  - WINSTALLFS
  - VINSTALLFS
  - You must create a
  - mkisofs
  - Messages similar to the following appear:
  - 210Ensure that there are no
  - -no-emul-boot
  - option once
  - -eltorito-alt-boot
  - Place a LIF directory at the start of the ISO image with the
  - instl_combine
  - Cdrecord
  - make_boot_tape
- 211How do I enable the X server and CDE during a golden image install
212Summary
For more information

22 pages384.76 Kb

1Table of Contents
3About this document
Intended audience
Advantage of running Ignite-UXunder Serviceguard
Setting up Ignite-UXto run under Serviceguard
4Procedure to set up Ignite under Serviceguard
1.Create an LVM volume group to manage the shared file systems
52.Create logical volumes for the shared file systems
63.Create mount points for the shared file systems
74.Add the -s option to /usr/lbin/tftpd
Mount
8Unmount
7.Configure group for exclusive access and export
8.Import volume group data on all cluster nodes
9.Copy NFS toolkit cluster scripts in place
910.Create package config and scripts
1112.Copy completed package directory to all nodes
13.Add the new package to the cluster on the first node
1214.Bring up the package on each node and install Ignite-UX
sgiux3
14Execute pkg_rec_depot on the first node only:
18Now move the package to the remaining nodes one at a time to
on each
15.Update the Ignite server IP address
19Best practices
20For more information

9 pages135.38 Kb

1Installing and Updating Ignite-UX
2Abstract
Getting the software
- Downloading Ignite-UXfrom the Web
- 3Obtaining Ignite-UXfrom OE and Application media
- 4Obtaining Ignite-UXfrom the recovery commands depot
5Installing and updating Ignite-UX
6Problems related to installing and updating Ignite-UX
- Cleaning up after an update (if needed)
- Dealing with obsolete HP-UXreleases
- 7Moving to an earlier version of Ignite-UX
- Identifying the source depot for Ignite-UXsoftware
- A change in the name of the full product bundle in version C.7.0 and later
- 8Mismatched filesets after updating to version C.7.0 or later