| Welcome to Huynh's Collections. We hope you enjoy your visit. You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. Join our community! If you're already a member please log in to your account to access all of our features: |
| How to install AIX 5L | |
|---|---|
| Tweet Topic Started: Jan 13 2007, 03:25 AM (600 Views) | |
| Huynhnb8x | Jan 13 2007, 03:25 AM Post #1 |
|
Th1nk
![]() ![]() ![]() ![]() ![]()
|
Installing the Base Operating System There are multiple ways to install the AIX base operating system. The Base Operating System (BOS) installation program first restores the run-time bos image, then installs the appropriate filesets, depending on your selections. The installation program automatically installs required message filesets, according to the language you choose. For more information about the installation options, refer to “BOS installation options” on page 40. The following installation methods are available on AIX: New and Complete Overwrite This method installs AIX 5.3 on a new machine or completely overwrites any BOS version that exists on your system. For instructions on installing AIX 5.3 on a new machine or to completely overwrite the BOS on an existing machine, refer to “Installing new and complete BOS overwrite or preservation” on page 52. Preservation This method replaces an earlier version of the BOS but retains the root volume group, the user-created logical volumes, and the /home file system. The system file systems /usr, /var, /tmp, and / (root) are overwritten. Product (application) files and configuration data stored in these file systems will be lost. Information stored in other non-system file systems will be preserved. For instructions on preserving the user-defined structure of an existing BOS, refer to “Installing new and complete BOS overwrite or preservation” on page 52. Migration This method upgrades from AIX 4.2, 4.3, 5.1, or 5.2 versions of the BOS to AIX 5.3 (see the release notes for restrictions). The migration installation method is used to upgrade from an existing version or release of AIX to a later version or release of AIX. A migration installation preserves most file systems, including the root volume group, logical volumes, and system configuration files. It overwrites the /tmp file system. For instructions on migrating an existing version or release of AIX to a later version or release of AIX, refer to “Migrating AIX” on page 145. The following table shows the differences in the installation steps among the installation methods. Table 7. AIX BOS Installation Methods Installation Steps New and Complete Overwrite Preservation Migration Create rootvg Yes No No Create file system /, /usr, /var Yes Yes No Create file system /home Yes No No Save Configuration No No Yes Restore BOS Yes Yes Yes Install Additional Filesets Yes Yes Yes Restore Configuration No No Yes Using BOS menus This topic describes the available choices on the BOS menu window. c Copyright IBM Corp. 2002, 2005 37 After you select the console and language to be used for the BOS menus, the Welcome to Base Operating System Installation and Maintenance window displays, as follows: Welcome to Base Operating System Installation and Maintenance Type the number of your choice and press Enter. Choice is indicated by >>>. >>> 1 Start Install Now with Default Settings 2 Change/Show Installation Settings and Install 3 Start Maintenance Mode for System Recovery 88 Help ? 99 Previous Menu >>> Choice [1]: Note: To turn on the debug mode for the BOS installation process, type 911 in the Choice field and press Enter. The Welcome to Base Operating System Installation and Maintenance window refreshes and the BOS installation process runs in debug mode when the installation occurs. Continue the procedure for selecting options and specifying data until the installation begins. Debug output is sent to the client’s display as the installation proceeds. If you select Start Install Now with Default Settings, the BOS command determines the default installation method to use based on your system’s configuration. A summary window displays, similar to the following, where you can confirm the installation method and installation options: Overwrite Installation Summary Disks: hdisk0 Cultural Convention: en_US Language: en_US Keyboard: en_US 64 Bit Kernel Enabled: No JFS2 File Systems Created: No Desktop: Enable System Backups to install any system: Yes Optional Software being installed: Kerberos_5 (Expansion Pack) >>> 1 Continue with Install 88 Help ? 99 Previous Menu >>> Choice [1]: If the selections are correct, press Enter to begin the BOS installation. However, if you would like to change the installation method or options, select Change/Show Installation Settings and Install at the BOS welcome window. The Installation and Settings window displays, as follows: 38 AIX 5L Version 5.3: Installing AIX Installation and Settings Either type 0 and press Enter to install with current settings, or type the number of the setting you want to change and press Enter. 1 System Settings: Method of Installation.............New and Complete Overwrite Disk Where You Want to Install.....hdisk0 2 Primary Language Environment Settings (AFTER Install): Cultural Convention................English (United States) Language ..........................English (United States) Keyboard ..........................English (United States) Keyboard Type......................Default 3 More Options (Desktop, Security, Kernel, Software, ...) >>> 0 Install with the current settings listed above. +----------------------------------------------------- 88 Help ? | WARNING: Base Operating System Installation will 99 Previous Menu | destroy or impair recovery of ALL data on the | destination disk hdisk0. >>> Choice [0]: For more information on the BOS menu options, refer to the Help at any time by typing 88 in the Choice field. Electronic license agreements AIX 5.3 ships with software license agreements that can be viewed electronically. If a product has an electronic license agreement, it must be accepted before software installation can continue. In the case of initial BOS installation, you can view and accept or reject license agreements in a license agreement dialog after the installation has occurred, but before the system is available for use as part of Configuration Assistant (graphics consoles) or Installation Assistant (ASCII consoles). The AIX BOS has a license agreement, but not all software packages do. When you agree to the license agreement for BOS installation, you are also accepting all license agreements for any software installed automatically with the BOS. Some software, such as the GNOME or KDE desktops, can be optionally installed during BOS installation; the appropriate licensing information for such software is displayed separately. If a customized bosinst.data file is used (usually for unattended installations, or nonprompted installations), the ACCEPT_LICENSES field in the control_flow stanza can be used to accept the license agreements so users are not prompted at reboot time. When performing a ″push″ installation using the Network Installation Management (NIM) environment, the licenses must be accepted, either from the choices made when initializing the installation or in a customized bosinst.data file, before the installation can continue. For more information about the bosinst.data file, refer to “The bosinst.data file” on page 42. For additional software package installations, the installation cannot occur unless the appropriate license agreements are accepted. This option, as well as options to preview licenses, is offered in both the System Management Interface Tool (SMIT) and the Web-based System Manager installation interfaces. When using the installp command, use the -Y flag to accept licenses and the -E flag to view license agreement files on the media. For more information about license manipulation, refer to the inulag command description in the AIX 5L |
| Knowledge crawling | |
![]() |
|
| Huynhnb8x | Jan 13 2007, 03:28 AM Post #2 |
|
Th1nk
![]() ![]() ![]() ![]() ![]()
|
BOS installation options This topic lists available options for installing BOS. The installation options are available by typing 3 in the More Options field in the Installation and Settings window. The following the installation options are available: Desktop The default is CDE for new and complete overwrite installations. If you select NONE, a minimal (tm) configuration is installed including X11, Java , perl, SMIT, and the Web-based System Manager (if Graphics Software is selected). If you select GNOME or KDE, the BOS installation process prompts you for the @@SWsym.AIX@@ Toolbox for Linux Applications CD. If this CD is not available, you can type q to continue the installation without the @@SWsym.AIX@@ Toolbox for Linux Applications CD. You can select additional desktops from the Install More Software menu. Enable Trusted Computing Base The Trusted Computing Base (TCB) is the part of the system that is responsible for enforcing the information security policies of the system. All of the computer’s hardware is included in the TCB, but a person administering the system should be concerned primarily with the software components of the TCB. If you install the Trusted Computing Base option, you enable the trusted path, trusted shell, and system-integrity checking (tcbck command). These features can be enabled only during BOS installation. The choices are yes and no. To enable the Trusted Computing Base, type 2 and press Enter. The default is no. Enable CAPP and EAL4+ Technology Available in a new and complete overwrite installation. If you enable Controlled Access Protection Profile (CAPP) and Evaluation Assurance Level 4+ (EAL4+), other restrictions exist on installation choices, such as: v Desktop = CDE or NONE v TCB = yes v 64-bit kernel = yes v JFS2 = yes v Enable System Backups to install any system (Installs all devices and kernels) = no v Install more software options = no information about CAPP and EAL4+, see Controlled Access Protection Profile and Evaluation For Assurance Level 4+ in the AIX 5L Version 5.3 Security Guide. Import User Volume Groups Available in migration installation and preservation installation. You have the option to have user volume groups imported after the installation completes. These volume groups can be manually imported at a later time. Enable 64-bit Kernel Available only on 64-bit Common Hardware Reference Platform (CHRP) systems. To toggle the choice between no (the default) and yes, type 3 and press Enter. If you choose no, the 64-bit kernel is still installed, but it is not linked to the running /unix. If you choose yes, the 64-bit kernel is installed and begins running when your system reboots. 40 AIX 5L Version 5.3: Installing AIX Create JFS2 File Systems Available in new and complete overwrite installation, as well as preservation installation with 64-bit kernel enabled option. Create enhanced journaled file systems during BOS installation. Graphics Software Available in new and complete overwrite installation, as well as preservation installation. Install graphics software support. Remove Java 1.1.8 Software Available in migration installation. You have the option to have all Java version 1.1.8 software removed. Enable System Backups If Enable System Backups to install any system is selected, all devices and kernels are installed, so that a system backup can be installed on a different system. For more information about installing a system backup to a different system, see “Cloning a system backup” on page 170. Install More Software Available in the new and complete overwrite installation method, as well as the preservation installation method. Select Install More Software to choose additional software to install after the BOS installation process finishes. A software bundle file corresponds to each selection that contains the required packages and filesets. The following software bundles are available: Install More Software 1. Mozilla (Mozilla CD).............................................. No 2. Kerberos_5 (Expansion Pack)....................................... No 3. Server (Volume 2)................................................ No 4. GNOME Desktop (Toolbox for Linux Applications).................... No 5. KDE Desktop (Toolbox for Linux Applications)...................... No >>> 0 Install with the current settings listed above. 88 Help ? 99 Previous Menu >>> Choice [0]: On 32-bit systems, the new and complete overwrite installation options are the following: Install Options 1. Desktop.......................................................... NONE, CDE, GNOME, KDE 2. Enable Trusted Computing Base.................................... No 3. Graphics Software................................................ Yes 4. Enable System Backups to install any system...................... Yes (Installs all devices and kernels) >>> 5. Install More Software 0 Install with the current settings listed above. 88 Help ? 99 Previous Menu >>> Choice [5]: On 64-bit systems, the new and complete overwrite installation options are the following: Installing the Base Operating System 41 Install Options 1. Desktop.......................................................... NONE, CDE, GNOME, KDE 2. Enable Trusted Computing Base.................................... No 3. Enable CAPP and EAL4+ Technology................................. No (English only, 64-bit kernel enablement, JFS2 file systems) 4. Enable 64-bit Kernel............................................. Yes 5. Create JFS2 File Systems......................................... Yes 6. Graphics Software................................................ Yes 7. Enable System Backups to install any system...................... Yes (Installs all devices and kernels) >>> 8. Install More Software 0 Install with the current settings listed above. 88 Help ? 99 Previous Menu >>> Choice [8]: On 64-bit systems, the preservation installation options are the following: Install Options 1. Desktop.......................................................... NONE, CDE, GNOME. KDE 2. Enable Trusted Computing Base.................................... No 3. Import User Volume Groups........................................ Yes 4. Graphics Software................................................ Yes 5. Enable System Backups to install any system...................... Yes (Installs all devices and kernels) >>> 6. Install More Software 0 Install with the current settings listed above. 88 Help ? 99 Previous Menu >>> Choice [6]: On 64-bit systems, the migration installation options are the following: Install Options 1. Enable Trusted Computing Base.................................... No 2. Import User Volume Groups........................................ Yes 3. Enable System Backups to install any system...................... Yes (Installs all devices and kernels) 4. Remove Java 1.1.8 Software....................................... No >>> 0 Install with the current settings listed above. 88 Help ? 99 Previous Menu >>> Choice [0]: The bosinst.data file This topic provides information on the content and use of the bosinst.data file. 42 AIX 5L Version 5.3: Installing AIX bosinst.data file stanza descriptions This section describes the contents of the bosinst.data file. Example files follow the stanza descriptions. (See “Using the bosinst.data file” on page 50.) bosinst.data control_flow stanza descriptions The control_flow stanza contains variables that control the way the installation program works. Variable Description CONSOLE Specifies the full path name of the device you want to use as the console. If this value is Default, and you are performing a nonprompted installation, then the console is set to /dev/lft0, if this device exists. If /dev/lft0 does not exist, the console is set to /dev/vty0 or /dev/tty0 depending on the system. (Instructions for which key to press are displayed on the screen.) If you change the PROMPT variable to no, you must specify a console here. INSTALL_METHOD Specifies a method of installation: migrate, preserve, erase_only, or overwrite (for a new and complete install). The default value is initially blank. The installation program assigns a value, depending on which version of AIX was previously installed. See “Installing the Base Operating System” on page 37 for more information. The default method of installation is migrate if a previous version of the operating system is on the machine. If no previous version exists, the default method is overwrite. The erase_only value specifies to erase the hard drives only and not to do an installation. PROMPT Specifies whether the installation program uses menus from which you make choices. The possible values are yes (default) and no. Note: You must fill in values for all variables in the locale stanza to uniquely identify the disk, if you set the PROMPT variable to no. Similarly, if PROMPT equals no, you must supply values for variables in the control_flow stanza, with two exceptions: the ERROR_EXIT and CUSTOMIZATION_FILE variables, which are optional. Attention: Fill in values for enough variables in the target_disk_data stanza if you set the PROMPT variable to no. The BOS installation program assigns target disks for blank variables. You can lose data if the installation program assigns a disk where you store data. Installing the Base Operating System 43 EXISTING_SYSTEM_OVERWRITE Confirms that the installation program can overwrite existing volume groups. This variable is applicable only for a nonprompted overwrite installation. The possible values are no (default), yes, and any. no (Default) Only disks that are not part of a volume group can be used for the installation. yes Disks that contain the root volume group is used first, and if additional disks are needed for the installation, then disks that contain no volume groups are used. any Any disks can be used for the installation. the installation is nonprompted and the target_disk_data When stanza is empty, the installation process uses the value of the EXISTING_SYSTEM_OVERWRITE field to determine the disks to install on. When you do a prompted installation, this value is changed to yes, and is saved with other changes in the /var/adm/ras/bosinst.data file. Network Install Manager (NIM) creates a default bosinst.data file (NIM bosinst_data resource) with this value set to yes, and system backups use the bosinst.data file that is copied from the /var/adm/ras directory, so in most cases this value is already be set to yes. If this field is set to no, as seen in the /usr/lpp/bosinst/bosinst.template file, an error message informs you that there are not enough disks matching the criteria needed to complete the installation during a non-prompted install. The BOS installation is then changed to a prompted BOS installation, and the value of the EXISTING_SYSTEM_OVERWRITE field is set to yes. INSTALL_X_IF_ADAPTER Specifies whether a desktop should be installed or not. The possible values are yes, all, and no. The default value for this field is yes, meaning that if the system has a graphical console, and a DESKTOP is specified, the DESKTOP is installed. If set to all and a DESKTOP is specified, the desktop is installed, whether the system has a graphical console or not. If set to no and a DESKTOP is specified, the desktop is not installed. RUN_STARTUP Starts the Configuration Assistant on first boot after the BOS installation completes, if the system has a graphical interface. Starts Installation Assistant if the machine has an ASCII interface. The possible values are yes (default) and no. The no value is valid only when the ACCEPT_LICENSES field is set to yes. RM_INST_ROOTS Removes all files and directories in the /usr/lpp/*/inst_roots directories. The possible values are no (default) and yes. The /usr/lpp/bos/inst_roots directories must remain if the machine is used as a network server. To save disk space, set this value to yes if the machine is not a network server. ERROR_EXIT Starts an executable program if an error occurs in the installation program. The default value is blank, which signals BOS installation to use a command that is shipped on the installation media. The command starts an error message routine when the installation program halts because of an error. As an alternative to the default, you can enter the path name of your own script or command for a customized error routine. CUSTOMIZATION_FILE Specifies the path name of a customization file you create. The default value is blank. The customization file is a script that starts immediately after the installation program concludes. 44 AIX 5L Version 5.3: Installing AIX TCB Specifies whether you want to install the Trusted Computing Base (TCB). When you install the TCB, the trusted path, the trusted shell, and system integrity checking are installed. The TCB must be installed and initialized when the operating system is installed. The TCB cannot be installed later. By not installing the TCB, installation time is reduced. The possible values are no (default) and yes. INSTALL_TYPE If set to CC_EVAL, then CAPP and EAL4+ technology will be enabled. This is only allowed when INSTALL_METHOD is overwrite. If this is set, the CULTURAL_CONVENTION and MESSAGES fields of the locale stanza can only be en_US or C. The system must be 64-bit, and have ENABLE_64BIT_KERNEL and CREATE_JFS2_FS set to yes. ALL_DEVICES_KERNELS must be set to no. TCB must be set to yes. DESKTOP can only be NONE or CDE. The additional software bundles: MOZILLA, HTTP_SERVER_BUNDLE, KERBEROS_5_BUNDLE, SERVER_BUNDLE and ALT_DISK_INSTALL_BUNDLE, must be set to no. BUNDLES Specifies what software bundles to install. Type the full path name of each bundle file. Be sure there is sufficient disk space and paging space on the target machine for the software you specify in the BUNDLES variable. This list of bundle file names is limited to 139 bytes. If your list of bundle file names is longer than 139 bytes, use the cat command to combine the bundle files into a single custom bundle file and enter the name of your custom bundle file in this field. If you are installing from tape, to specify system-defined bundles on the product media, use the full path name of each bundle file as follows: /usr/sys/inst.data/sys_bundles/BundleFileName If you are using a bosinst.data diskette to define your own bundle files, specify the full path name of each bundle file as follows: /../DirectoryName/BundleFileName. For example, if you put a bundle file named mybundle in the root directory, the full path name would be /../mybundle. If you are using preservation installation, create bundle files before you start the installation. Create the files in /home and specify the full path name of each bundle file as follows: /home/BundleFileName Installing the Base Operating System 45 RECOVER_DEVICES Specifies whether to reconfigure the devices. The default value is Default. For mksysb installations, the ODM configuration database is saved in the image. The device names and attributes are automatically extracted from the database, and the BOS installation program attempts to recreate the devices the same way they were on the machine the mksysb was created on. This is normal procedure for regular mksysb restores on the same system. However, for cloning (installing the mksysb image on another system), you may not want these devices configured this way, especially for network configuration. When the mksysb image is created, the CPU ID is saved. If you are reinstalling the same system, then the device information is recovered. If the mksysb image is used to install another system, device information is not recovered from the mksysb image. The Default value can be overwritten. For example, if your system had the planar replaced, or you upgraded to another system, you might want to recover devices. In these cases, you can select yes in the Backup Restore menu to recover devices. BOSINST_DEBUG Specifies whether to show debug output during BOS installation. The value yes sends set -x debug output to the screen during BOS installation. The possible values are no (default) and yes. ACCEPT_LICENSES Specifies whether to accept software license agreements during the BOS installation. The default is no. To automatically accept them, set this value to yes. When the software licenses agreements are not accepted during BOS installation, Configuration Assistant or Installation Assistant prompts you to view and accept them. During a BOS installation, if this value is blank, the default of no is assumed. For mksysb installations, when the ACCEPT_LICENSES field is no, the user is forced to accept the licenses again before continuing to use the system. When the ACCEPT_LICENSES field is set to yes, the licenses are automatically accepted for the user. If blank, the state of the licenses is the same as when the mksysb was created. DESKTOP Specifies the desktop to be installed. The choice of available desktops are CDE (the default), NONE, GNOME, and KDE. If you choose GNOME or KDE, you will be prompted for the AIX Toolbox for Linux Applications CD. INSTALL_DEVICES_AND_UPDATES When installing a mksysb image to a system with a different hardware configuration, boot from product media to get any missing device drivers installed. In addition, if the product media is a later level of AIX than the mksysb, software in the mksysb image will be updated. To prevent either of these additional installations from occurring, set this field to no. The default is yes. IMPORT_USER_VGS Specifies whether you want any user volume groups to be automatically imported after the system has been installed. The choices are yes and no. ENABLE_64BIT_KERNEL Specifies whether you want to enable the 64-bit kernel. The choices are yes and no. CREATE_JFS2_FS Specifies whether you want to create enhanced journaled file systems. The choices are yes and no. 46 AIX 5L Version 5.3: Installing AIX ALL_DEVICES_KERNELS Specifies whether to install all device and kernel filesets. The choices are yes and no. If you select no, your system will be installed with the devices and kernel specific to your system configuration. If you select yes, when you create a system backup of your system, you can use that system backup to install any system. GRAPHICS_BUNDLE Specifies whether to install the graphics software bundle during the BOS installation. This software bundle contains the graphics support for the Web-based System Manager and Linux desktops. The choices are yes and no. MOZILLA_BUNDLE Specifies whether to install the Mozilla software bundle during the BOS installation. This software bundle contains the Mozilla Web browser software. The choices are yes and no. KERBEROS_5_BUNDLE Specifies whether to install the Kerberos 5 client software bundle during the BOS installation. This software bundle installs the Kerberos 5 client software. The choices are yes and no. SERVER_BUNDLE Specifies whether to install the AIX server software bundle during the BOS installation. This software bundle installs additional networking software, performance tools, and accounting services software. The choices are yes and no. ALT_DISK_INSTALL_BUNDLE Specifies whether to install the alternate disk installation software during the BOS installation. The choices are yes and no. REMOVE_JAVA_118 Specifies whether to remove the Java 1.1.8 software from the current system when performing a migration installation. The choices are yes and no. HARDWARE_DUMP Creates a dump logical volume to contain firmware and hardware dump data. Dump logical volumes are only create on hardware that supports creation of firmware and hardware dump data. The choices are yes and no. ERASE_ITERATIONS Specifies the number of times to erase the choosen hard drives before the installation occurs. This field is only valid when the INSTALL_METHOD field is set to overwrite or erase_only. The choices for this field is a number from 0 to 8. If the field is set to 0 then no erasure of the hard drives will occur. The default is 0. ERASE_PATTERNS Specifies the patterns to write to the choosen hard drives. The value for this field is a comma separated list of the patterns to use for each erasure of the drives. A valid pattern is a hexadecimal value from 0 to ffffffff. The number of patterns specified must be equal or greater to the number of iterations specified in ERASE_ITERATIONS. If ERASE_ITERATIONS is 0 then this field is ignored. ex: If ERASE_ITERATIONS = 3 then a valid entry for this field could be ERASE_PATTERNS = 00,ff,0a0a0a0a . ADD_CDE Adds CDE as an additional desktop. If the DESKTOP field is not CDE and ADD_CDE is set to yes, the CDE desktop is installed in addition to the desktop specified by the DESKTOP field. The default value is no. If DESKTOP is set to none, this attribute is ignored. ADD_KDE Adds KDE as an additional desktop. If the DESKTOP field is not KDE and ADD_KDE is set to yes, the KDE desktop is installed in addition to the desktop specified by the DESKTOP field. The default value is no. If DESKTOP is set to none, this attribute is ignored. ADD_GNOME Adds GNOME as an additional desktop. If the DESKTOP field is not GNOME and ADD_GNOME is set to yes, the GNOME desktop is installed in addition to the desktop specified by the DESKTOP field. The default value is no. If DESKTOP is set to none, this attribute is ignored. Installing the Base Operating System 47 MKSYSB_MIGRATION_DEVICE When set, specifies the device to be used to restore the mksysb image for migration. Default is blank. Valid values are /dev/cddevice number for a mksysb image on a CD-DVD, and /dev/rmtdevice number for a mksysb image on tape. For a network installation, the valid value is the word network. |
| Knowledge crawling | |
![]() |
|
| Huynhnb8x | Jan 13 2007, 03:29 AM Post #3 |
|
Th1nk
![]() ![]() ![]() ![]() ![]()
|
bosinst.data target_disk_data stanza The target_disk_data stanza contains variables for disks in the machine where the program is to install BOS. The default bosinst.data file has one target_disk_data stanza, but you can add new stanzas to install BOS on multiple disks, one stanza for each disk. Multiple target_disk_data stanzas can exist. They define the disks that are to contain the root volume group. Only one field (PVID, PHYSICAL_LOCATION, SAN_DISKID, CONNECTION, LOCATION, SIZE_MB, HDISKNAME) must be non-null for BOS installation to choose a disk. The order of precedence is PVID (Physical Volume ID), PHYSICAL_LOCATION, SAN_DISKID, then CONNECTION (parent attribute//connwhere attribute), then LOCATION, then SIZE_MB, and then HDISKNAME. The BOS installation process uses the following logic to determine how to use the target_disk_data stanza information: v If PVID is set, BOS installation checks to see if a disk matches the value. If so, other attributes are ignored. v If PVID is empty and PHYSICAL_LOCATION is set, then BOS installation checks to see if the parent and connwhere attributes (separated by ″//″) match a disk. If they do, other attributes are ignored. v If either PVID or PHYSICAL_LOCATION is set, and neither value matches a disk on the target system, and no other attributes are set, an error message is generated, and a disk must be explicitly selected. v If PVID and PHYSICAL_LOCATION are empty, and SAN_DISKID is set, then, for fibre channel-attached disks, BOS installation interprets the SAN_DISKID as a World Wide Port Name and a Logical Unit ID (separated by ″//″). The World Wide Port Name (ww_name) and Logical Unit ID (lun_id) can be obtained on a running system from the lsattr command. The SAN_DISKID field is checked before the CONNECTION field. v If the ww_name and lun_id match a disk, other attributes are ignored. v If either PVID or SAN_DISKID is set, and neither value matches a disk on the target system, and no other attributes are set, an error message is generated and a disk must be explicitly selected. v If PVID and SAN_DISKID are empty and CONNECTION is set, BOS installation verifies if the parent and connwhere attributes (separated by ″//″) match a disk. If this is true, other attributes are ignored. v If CONNECTION is set, the value does not match a disk on the target system, and no other attributes are set, an error message is generated and a disk must be explicitly selected. v If other attributes are specified, processing occurs as described below: - If LOCATION is set, BOS installation ignores SIZE_MB and HDISKNAME. - If LOCATION is not set and SIZE_MB is, BOS installation selects disks based on SIZE_MB and ignores HDISKNAME. - If LOCATION and SIZE_MB are both empty, BOS installation chooses the disk specified in HDISKNAME. - If all fields are empty, BOS installation chooses a disk for you. For the PVID, PHYSICAL_LOCATION, SAN_DISKID, and CONNECTION fields, the BOS installation process uses the following logic to determine how to use the target_disk_data stanza information: v Does the information in one or more of the PVID, PHYSICAL_LOCATION, SAN_DISKID, and CONNECTION fields match the disk information? v If the disk information matches the information in one of these four fields, use that information. 48 AIX 5L Version 5.3: Installing AIX v If the disk information does not match the information in one of these four fields, and if the LOCATION, SIZE_MB, and HDISKNAME fields are not set, display an error message and prompt the user for the correct disk information. PHYSICAL_LOCATION information can be retrieved using the lsdev command. For example: The # lsdev -Cc disk -l hdisk0 -F "name physloc" returns the hdisk0 diskname and the P2/Z1-A8 physical location. Attention: If prompt=no, do not leave the target_disk_data stanzas empty, unless it is unimportant which disk BOS installation overwrites. This is because the algorithm that determines the default disk for the installation is not always predictable. SIZE_MB field can contain either a size or the word largest. If a size is listed, BOS installation does The a ″best-fit″ on the disks. If the word largest is in that field, BOS installation selects the largest disk. If there is more than one target_disk_data stanza, BOS installation selects the two ″largest″ disks, and so on. PVID Specifies the 16-digit physical volume identifier for the disk. PHYSICAL_LOCATION The physical location code provides a way to identify fibre channel disks during BOS Install. For fibre channel disks the PHYSICAL_LOCATION field includes the World Wide Port Name and Lun ID that are included in the SAN_DISKID field. The information in the PHYSICAL_LOCATION field supercedes the information in the SAN_DISKID field. SAN_DISKID Specifies the World Wide Port Name and a Logical Unit ID for fibre channel-attached disks. The ww_name and lun_id are separated by two slashes (//). This information can be obtained on a running system from the lsattr command. CONNECTION Specifies the combination of the parent attribute and the connwhere attribute associated with a disk. The parent and connwhere values are separated by two slashes (//). If the parent value is scsi0 and the connwhere value is 0,1, then the CONNECTION value is scsi0//0,1. An example of the CONNECTION value for a SSA disk would be ssar//000629CCC07300D. In the example, the parent attribute is represented by ssar and the ConnectionLocation (15-character unique identity) of the disk drive 000629CCC07300D is used for the connwhere attribute. SIZE_MB Specifies the formatted size of the disk, in megabytes, where the program is to install BOS. The default value is blank. You can specify the size of your target disk by typing the number of megabytes available on the formatted disk. Also, you can type largest if you want to use the largest disk (that has not already been selected) found by the installation program. LOCATION Specifies a location code for the disk where the program is to install BOS. The default value is blank. If you do not specify a value, the installation program assigns a value based on the next two variables. For more information about physical location codes, refer to the Diagnostic Information for Multiple Bus Systems guide. HDISKNAME Specifies the path name of the target disk. The default value is blank. To name a target disk, use the hdiskname format, where hdiskname is the device name of your disk (for example, hdisk0). bosinst.data file locale stanza The locale stanza contains variables for the primary language that the installed machine is to use. Refer to Understanding Locale Categories in AIX 5L Version 5.3 National Language Support Guide and Reference, which provides information about locales and the format to use when editing variables. BOSINST_LANG Specifies the language that the installation program uses for prompts, menus, and error messages. The default value is blank. CULTURAL_CONVENTION Specifies the primary locale to install. The default value is blank. MESSAGES Specifies the locale for message catalogs to install. The default value is blank. KEYBOARD Specifies the keyboard map to install. The default value is blank. Installing the Base Operating System 49 bosinst.data large_dumplv stanza The optional large_dumplv stanza specifies characteristics used if a dedicated dump device is to be created on the systems. A dedicated dump device is only created for systems with 4 GB or more of memory. The following characteristics are available for a dedicated large dump device: DUMPDEVICE Specifies the name of the dedicated dump device. SIZEGB Specifies the size of the dedicated dump device in gigabytes. If the stanza is not present, the dedicated dump device is created when required. A dedicated dump device is created in machines with at least 4 Gigabytes of real memory during an overwrite install. By default, the name of the dedicated dump device is lg_dumplv and its size is determined by the following formula: 4>= RAM < 12 size of dump device= 1 GB 12>= RAM < 24 size of dump device= 2 GB 24>= RAM < 48 size of dump device= 3 GB RAM >= 48 size of dump device= 4 GB bosinst.data dump stanza The dump stanza specifies system dump characteristics. PRIMARY Specifies the primary dump device to be set by sysdumpdev -P -p device. SECONDARY Specifies the secondary dump device to be set by sysdumpdev -P -s device. COPYDIR Specifies the directory to which the dump is copied at system boot. FORCECOPY Specifies whether the system boots into menus that allow copy of the dump to external media if the copy fails. ALWAYS_ALLOW Specifies whether the key mode switch can be ignored when a dump is requested. If the stanza is not present in the bosinst.data file, no additional dump-device handling occurs beyond what is already in place. Checking on the values of the fields is limited; if the device specified for a dump device is not valid, any error processing comes from the sysdumpdev command and is sent to the console and stored in the BOS installation log. v If FORCECOPY is specified and no COPYDIR is specified, the value field of the autocopydump attribute from /etc/objrepos/SWservAt is retrieved and used for the sysdumpdev -[d|D] copydir operation. v If only the COPYDIR is specified without FORCECOPY being specified, forcecopy defaults to yes. The sysdumpdev -d (FORCECOPY = no) or sysdumpdev -D (FORCECOPY = yes) is used to set the copy directory. v If ALWAYS_ALLOW=yes, run sysdumpdev -K. Otherwise, run sysdumpdev -k. v If any values other than yes and no are specified for FORCECOPY or ALWAYS_ALLOW, the default actions occur, and processing continues. v If no value is specified for a particular dump field, no analogous sysdumpdev operation is performed. This leaves the system values in the appropriate state, even for a migration or system backup image installation. If a COPYDIR is specified but FORCECOPY is not specified, the value of the forcecopydump attribute is retrieved from the /etc/objrepos/SWservAt file to determine the correct form of sysdumpdev to invoke. Using the bosinst.data file This topic introduces an example bosinst.data file that shows you how to customize a nonprompted network installation. 50 AIX 5L Version 5.3: Installing AIX The values in the bosinst.data file for this example are not specific to a network installation and can be applied for other types of installations, such as a mksysb installation. Note: The depicted values illustrate formatting only and do not apply to your installation. information about a bosinst.data variable or values, see “bosinst.data file stanza descriptions” on For page 43. To check the contents of your customized bosinst.data file, use the bicheck command, as follows: /usr/lpp/bosinst/bicheck filename bosinst.data file nonprompted network installation This topic provides an example of a modified bosinst.data file that might be used in a nonprompted network installation. control_flow: CONSOLE = Default INSTALL_METHOD = overwrite PROMPT = no EXISTING_SYSTEM_OVERWRITE = yes INSTALL_X_IF_ADAPTER = yes RUN_STARTUP = yes RM_INST_ROOTS = no ERROR_EXIT = CUSTOMIZATION_FILE = TCB = no INSTALL_TYPE = BUNDLES = RECOVER_DEVICES = no BOSINST_DEBUG = no ACCEPT_LICENSES = yes DESKTOP = NONE INSTALL_DEVICES_AND_UPDATES = yes IMPORT_USER_VGS = ENABLE_64BIT_KERNEL = Default CREATE_JFS2_FS = Default ALL_DEVICES_KERNELS = yes GRAPHICS_BUNDLE = yes MOZILLA_BUNDLE = no KERBEROS_5_BUNDLE = no SERVER_BUNDLE = no REMOVE_JAVA_118 = no HARDWARE_DUMP = yes ADD_CDE = no ADD_GNOME = no ADD_KDE = no ERASE_ITERATIONS = 0 ERASE_PATTERNS = target_disk_data: LOCATION = SIZE_MB = HDISKNAME = locale: BOSINST_LANG = CULTURAL_CONVENTION = MESSAGES = KEYBOARD = |
| Knowledge crawling | |
![]() |
|
| « Previous Topic · Tài liệu sưu tầm · Next Topic » |
| Track Topic · E-mail Topic |
9:00 AM Jul 11
|
Theme by James... of the ZBTZ and themeszetaboards.com





![]](http://z5.ifrm.com/static/1/pip_r.png)



9:00 AM Jul 11