HP Ignite-UX Impacts statements

"PS2_DIN_Canada_TBITS-3", "PS2_DIN_Canadian_French", "PS2_DIN_Czech", "PS2_DIN_Czech_Euro", "PS2_DIN_Danish", "PS2_DIN_Danish_Euro", "PS2_DIN_Euro_Spanish", "PS2_DIN_Euro_Spanish_Euro", "PS2_DIN_French", "PS2_DIN_French_Euro",

...

"PS2_DIN_T_Chinese", "PS2_DIN_Turkish", "PS2_DIN_UK_English", "PS2_DIN_UK_English_Euro", "PS2_DIN_US_English", "PS2_DIN_US_English_Euro"

}

}

has_usb { _hp_keyboard += {

"USB_PS2_DIN_Belgian", "USB_PS2_DIN_Belgian_Euro", "USB_PS2_DIN_Danish", "USB_PS2_DIN_Danish_Euro", "USB_PS2_DIN_Euro_Spanish", "USB_PS2_DIN_Euro_Spanish_Euro",

…

"USB_PS2_DIN_Swiss_French2_Euro", "USB_PS2_DIN_Swiss_German2", "USB_PS2_DIN_Swiss_German2_Euro", "USB_PS2_DIN_T_Chinese", "USB_PS2_DIN_UK_English", "USB_PS2_DIN_UK_English_Euro", "USB_PS2_DIN_US_English", "USB_PS2_DIN_US_English_Euro"

}

}

init _hp_keyboard = "Not_Applicable"

Impacts statements

Previous sections have explained impacts statements and the circumstances in which they may not accurately represent space usage. This section describes how to structure your impacts, and what level to use with your impacts - such decisions may not be straightforward.

HP-UX installation media is discussed first. The impacts statements on the installation media are all at level one. Consider what limitations this may cause, that is, what problems the following set of (partial) impacts could cause:

impacts = "/usr" 687920Kb impacts = "/opt" 95300Kb impacts = "/var" 23395Kb

Most people encounter no problems. The previous statements assume that you did not create any extra file systems apart from the default file systems that Ignite-UX would create. The impacts do not cause a problem for most people, because Ignite-UX only creates file systems at the top level by default, for example: /home, /var, /opt, and /usr.

116

Contents

Ignite-UXCustom Configuration Files Page Page Page Page Abstract Introduction Typographic Conventions HP-UX11i release names and release identifiers Configuration files and INDEX files The CINDEX file CINDEX CINDEX make_net_recovery file is created and managed file is the same as the INDEX The global config.local file /var/opt/ignite/config.local The recovery config.local file For make_net_recovery, if the file For Testing 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: What 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 The make_net_recovery configuration files make_net_recovery The three configuration files are as follows: 1.system_cfg – save_config Using the manage_index command Adding 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 Adding scripts to the INDEX file scripts Advanced Removing cfg clauses from an INDEX file "testing two Setting the default cfg clause in an INDEX file Listing the names of cfg clauses in an INDEX file For example: Listing 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: Creating a new cfg clause from an existing clause manage_index Removing a configuration file from a cfg clause “testing” config_c Removing a script from an INDEX file The following example adds a script and then removes it: List the names of all configuration files in a cfg clause Using the make_bundles command The make_bundles first form The examples in this section operate on the following depot: The following example bundles all the patches: ======= 08/30/07 16:25:13 EST END swpackage SESSION PHCO_33976 Now the depot lists two revisions of the bundle: PB_Sept_2007 Now we can create the PSF file You can then package the bundle manually: The make_bundles second form Page The make_bundles third form [-l file| product/fileset...] depot_path Next, you create another PSF but this time with the extra pax patch PHCO_33967: Using the instl_dbg command Combining instl_dbg and itool Running instl_dbg /var/opt/ignite/clients/<MAC amount shy (KB) Page Page Page Other 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 <MAC never Miscellaneous configuration tips Analyzing the HP-UXdefault B.11.11 cfg clause must As of Ignite-UXC.6.0.x, the release keyword is checked against the value of the _hp_ikernel_os_release Table <variable> visible_if false Additional is_hppa unifdef unifdef init _hp_disk_layout "_hp_disk_layout="… _hp_disk_layout _hp_disk_root _hp_primary_path Page (<variable>={ value1, value2, … hp_pri_swap Root Swap (MB) [_hp_root_disk enum YES Now 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 /usr /var _hp_disk_layouts _hp_disk_config ∙A physical_volume definition minfree _hp_group_name A 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 physical_extent_size vgdisk bad_block _relocate Page Page stripes _hp_FS_stripe_size /opt /var/adm/crash /tmp /export /home autoboot setboot _hp_force_autoboot disable_dhcp=true] The last part of configuration accomplishes several things: 1.Sets the os_release attribute for the swinstall command line Analyzing the HP-UXdefault B.11.31 cfg clause Please note the following text from the Ignite-UXC.7.0 release notes: _hp_ikernel_os_release B.11.31 does not support 9000/7xx workstation systems B.11.31 requires at least 1GB of system memory _hp_efi_partition_size enum _hp_efi_partition is_ia64 File System Page Page Page [_hp_root_disk].model FALSE _hp_min_swap Page A volume group definition must have the following: *=<index max_physical_extents Page bad_block _relocate "Create separate volumes (/usr, /var, ...) Logical Volume Manager (LVM) with HFS Page Create /export volume TRUE Page Page Page Special variables _hp_locale _hp_cfg_detail_level _hp_pri_swap _hp_min_swap _hp_disk_layout 1.Enter: Change the type of disk layout by selecting the Quit the Edit and remove _hp_default_cur_lan_dev _hp_default_final_lan_dev _hp_keyboard _hp_root_disk _hp_boot_dev_path _hp_primary_path _hp_primary_partition_size _hp_efi_partition_size _hp_service_partition_size _hp_root_grp_disks _hp_root_grp_striped _hp_addnl_fs_free_pct _hp_ignore_sw_impact tmp/a _hp_custom_sys _hp_lanadmin_args _hp_nfs_mount_opts _hp_nfs_mount_retries _hp_tftp_cmds _hp_hide_other_disks _hp_saved_detail_level _hp_os_bitness _hp_force_autoboot _hp_ikernel_os_release _hp_current_client_release _HP_CLONING _hp_console_verbosity _hp_patch_save_files _hp_umask _hp_ht_enable _hp_debug_level Configuration for software to be installed 32-bitsystems): b_PHSS_28764 T1335AC corequisite autoselect_patches=true Page /var/opt/ignite/data/Rel_B.11.11/vpars_A.02.03.02.cfg architecture vendor revision number version number Core operating system depot configuration Page sw_sel "OE90BaseOS64 "English "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 Page Software HPUXBaseOS ps2 has_ps2 Not Applicable Impacts statements Page Overstated SD impacts Categories and other Ignite-UXsoftware attributes cat The following is what is special about these categories: OpEnvironments Environments: HPUXBase32 Looking at a network recovery sw_source and sw_sel Page Using a sw_sel to run commands instead of installing software Using a sw_sel to apply kernel parameters KernelConfig set_kernel exrequisites sw_sel "B9789AA, r=1.3.1.09.08 sw_sel "Kernel Config for Java "Kernel Config for Servers "Kernel Config for Workstations mod_kernel rm_kernel tunable Forcing software (sw_sel) clauses to be installed Automating dependencies in software See "Using a sw_sel to apply kernel parameters" for exrequisite examples fnmatch (3) Configuration for volume and disk groups Overview Configuration examples The test on to the variable set is only evaluated once. If Next is the definition of the disk layout Custom configuration for Product XYZ: _my_volume_group Product XYZ – 4GL Page The last volumes are defined as follows: usage = LVM usage = VXVM Example Two (selection of disk layout based on hardware) Custom configuration rp8400 w/18GB disks warning Example Three (be careful what you ask for, you just might get it) disk[_hp_root_disk].size During installation those errors would look like: Part A (custom configuration in installation file system) Part B (Installation file system custom network config) Part A (restricting the values that a variable can take using an enum) Part 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: Example Seven (regular expression matching) You can give a character class in the regular expression, for example Do not use the construct zero – E Another example: Testing this with grep you can see that this does work: would match: 1.Something that starts with “ab“ 2.Something that contains “cd“ Configuration parameters in the installation file system dhcp_server dhcp_server = "10.0.0.53 dhcp_server[0/0/0] = "10.0.0.54 dhcp_misc_opts dhcp_misc_opts Problems that can be solved with _hp_lanadmin_args _hp_lanadmin_args only Control Environment variables env_vars tztab INST_NET_RESPONSE_TIMEOUT— If this value is set to >0 the following message appears: Managing configurations with unifdef The unifdef command recognizes the following C preprocessor directives: With these directives, you can change the configuration file as follows: Coping with auto_adm and boot changes in HP-UXB.11.23 CONF data auto_conf CONF default message label ISL data Creating new files Adding new menu entries to a file Using an "append" file Updating a menu entry in a file Deleting a menu entry from a file Changing the default menu choice Changing the timeout Updating the prompt message Into and out of an LIF file Installation configurations using Software Distributor depots How to configure instl_bootd instl_bootd How to setup depots up remote to the Getting 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 /var/opt/ignite/depots/Rel_B.11.11/core /var/opt/ignite/logs/make_depots Operating 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 Using the Ignite-UXGUI 2.Select Run Tutorial/Server Setup… from the Actions menu Server Setup The third step Set up Software Next Copy CD/DVD Use CD/DVD 6.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 Page Cancel The pitfalls of using multiple media This 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: Creating a minimalist cfg clause for installation When complete you have a new cfg clause in the INDEX file: Creating the application depot Creating a configuration for the application depot An example problem Follow on consequences Package an application in SD format Define an application in a non-SDformat Base OS MyApp Required Additional system hardware tests are explained in the following section Using noncore.cfg to define applications noncore.cfg /opt/ignite/data/examples/noncore.cfg noncore.cfg 9000 The 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 SD and archive bitness comparison wlist fileset name HP-UX:*64 Adding the non-SDapplication configuration file to the INDEX file Setting up the depot Packaging the patches into a bundle Generating a configuration Customizing configuration In the current INDEX file, you have the following cfg clause: Page Performance considerations for SD-UXbased installs Tuning SD-UXfor concurrent access /usr/lib/sw/sys.defaults swagentd.rpc_max_calls=n rpc_max_calls # swagentd –r –xrpc_max_calls=n Memory and the buffer cache Network Bandwidth Installation configurations using golden images /opt/ignite/data/Rel_B.xx.yy/config core11.cfg archive post_load_script os_arch_post_l /var/opt/ignite/scripts post_load|config_scripts /opt/ignite/data/scripts golden image - 32 bit OS !can_run_64bit can_run_64bit English The format of a entry in the locale list is: <locale "locale -a ja_JP.SJIS Instances that may require modifying os_arch_post_l os_arch_post_l /usr/newconfig merge_file merge_file /etc/hosts Creating a golden image make_sys_image make_sys_image Final words about golden image installations config.local Understanding what is_net_info_temporary does Understanding how VxFS file system versions are set How do I… How 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 How 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 Create 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: not IINSTALLFS output WINSTALLFS VINSTALLFS Ensure 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 How do I enable the X server and CDE during a golden image install Summary For more information