1. Introduction. 2. TPM, pseries and AIX NIM Environment

Transcription

1 1. Introduction This paper is to describe the following functions of Tivoli Provisioning Manager (TPM) with the automation packages of pseries-server and NIM that are installed with TPM and Tivoli Intelligent Orchestrator (TIO). Discovery of existing Power 5 or Power 4 managed system and LPARs associated with that managed system from the Hardware Management Console (HMC). Management of LPARs with operations of delete, power on, power off and increase, decrease allocations for CPU, memory. Creation of a new LPAR. Setup and discovery of NIM. Capture mksysb image to NIM server. Definition of scripted install image to NIM server. Install of a AIX mksysb image with power up, network boot of powered down LPAR. Install of a software product containing AIX filesets. Install of a software stack containing an AIX image and other software products. This paper does not attempt to replace the pseries and NIM automation package documentation which should be reviewed for more detailed information. The paper has been written to illustrate the functions of TPM with pseries and NIM. The automation package documentation can be viewed by navigating in the TPM User Interface (UI) to Automation > Device Drivers. For pseries-server continue navigating to HostPlatform > pseries Host Platform > Documentation tab > Package and for NIM to Boot Servers > NIM BootServer > Documentation tab > Package. 2. TPM, pseries and AIX NIM Environment

2 The following systems are in this environment: Power 5 managed system TP SN10FB28C model with four existing LPARs mmaix1, mmaix2, mmaix4, mmaix5 and a Virtual I/O server todvios2. xseries system zoo running TPM V5.1 FP2 or TIO V5.1 FP2. Hardware Management Console (HMC) power5hmc that controls the managed system Network Installation Management (NIM) server nimster with mksysb images and to provide AIX BOS install operations. 3. Discovery of pseries Environment Hardware Management Console (HMC) provides a command line interface. The TPM pseries- Server automation package provides workflows that execute HMC commands to query, dynamically create, modify, or delete LPAR definitions. TPM can interface with the HMC to remotely invoke the HMC commands via secure shell protocol (SSH). Existing pseries Power 5 or Power 4 managed system(s) can be discovered from TPM with commands executed on the HMC. To perform this HMC discovery perform the following actions: Define a computer for the HMC by navigating in TPM UI to Inventory > Manage Inventory > Computers > Edit > Add Computer. After computer is defined, click on the Credentials tab to define the SSH and SCP Service Access Point (SAP) as a password credential or a RSA credential. RSA credentials require public key of the TPM user tioadmin to be added to the authorized_keys2 file of the HMC userid hscroot. Another HMC userid instead of hscroot could be used but needs to be defined with the HMC roles of super administrator or operator. For HMC to accept commands from an external source such as TPM, the HMC remote command execution feature must be enabled. From the HMC GUI, select HMC Maintenance > System Configuration > Enable/Disable Remote Command Execution and then select the checkbox for Enable Remote Command Execution Using the ssh Facility. TPM Logical Device Operation (LDO) of Device.ExecuteCommand can be executed on the deviceid of this HMC computer with ExecuteCommand of ls and no WorkingDirectory since HMC is a restricted shell environment to test that TPM can remotely execute commands. Define the Discovery Configuration for HMC Discovery by navigating in TPM UI to Inventory > Manage Discovery > Discovery Configurations > Edit > Add Discovery Configuration with Discovery Method of HMC Discovery. Discovery parameter of server needs to be defined for the TPM computer representing the HMC. Discovery parameter of cec is to discover an individual HMC managed system. No discovery parameter for cec will discovery all HMC managed systems. The LPAR name will be the TPM computer name. A DNS lookup of the TPM computer name for a LPAR with a single Network Interface Card (NIC) is done to define the network interface with the IP address. The manual definition of the network interface does not need to be done prior to install AIX image if the LPAR name is defined in DNS with a valid IP address. HMC discovery does not define the network interfaces for an LPAR with multiple NICs. HMC discovery is a discovery executing HMC commands and does not access the operating system with credentials to obtain the IP addresses for all the network interfaces and determine which is the management IP address. Discovery Computers with SSH could be executed after HMC discovery on TPM computers for LPARs with multiple NICs and an operating system. Run the HMC discovery configuration defined by clicking on the right hand side button and click Run and then click Submit. Monitor task for successful completion.

3 The HMC console is shown with the managed system TP SN10FB28C highlighted to be discovered with the associated LPARs. After HMC discovery completes, the following is discovered from the pseries environment which can be seen by navigating in TPM UI to Inventory > Manage Inventory > Computers. Computer TP SN10FB28C is the managed system with the physical hardware resources to be shared or virtualized. Under the General tab of this computer is the hardware resources as shown with the diagram Managed System Hardware. Computer TP SN10FB28C shows the resource allocations from the LPARs for hard disk, CPU and memory as shown with the diagram Managed System Resource Allocations. Viewing the hardware resources and resource allocations will show you how much of the managed system resources are allocated and how much is free for future allocations. Computers mmaix1, mmaix2, mmaix4, mmaix5 are LPAR partitions discovered. Physical hardware resources and resource allocations are shown for the individual LPAR on the General tab of the computer. Computer todvios2 is the Virtual I/O server in a LPAR partition discovered. The Virtual I/O server allocates logical volumes of the non-rootvg volume group requested that are mapped to volume groups on other LPAR partitions.

4 Managed System Hardware Managed System Resource Allocations

5 4. Management of LPAR partitions Computers mmaix1, mmaix2, mmaix4, mmaix5 are LPAR partitions discovered that can be managed with operations to delete, power on, power off, reboot and change the CPU, memory allocations. Each of these operations can be performed by navigating in the TPM UI to Inventory -> Manage Inventory -> Computers. Click on the right hand side button of the computer to see actions of Delete using workflow, Power On and Power Off. Click on the General tab of the computer. Then click Management > Hardware Reboot to reboot. If you are using a pseries Power 5 environment, then Micro-Partitioning allows allocation in increments of 1/10 of a physical CPU from the managed system. The Host Platform Quantity would be the physical managed system resource and the Virtual Quantity is the whole number of resources seen by the operating system. To change the CPU and memory allocations of a LPAR: Click on the General tab of the computer and under Allocated Resources are existing allocations for the LPAR with resource type of CPU and Memory. Click on the right hand side button to see actions of Increase Allocation and Decrease Allocation. To increase or decrease allocation for memory, specify the same value in MB for the Increase Virtual Quantity and Increase Host Platform Quantity. To increase or decrease allocation for CPU, specify the same whole number value for the Virtual Quantity and Host Platform Quantity in a Power 4 environment. Power 5 environment Micro-Partitioning is used when the virtual quantity is not equal to the host platform quantity where the host platform quantity can be a multiple of 0.10 physical processor units and the virtual quantity is a whole number of processors seen by the operating system. This diagram shows increasing a Power 5 LPAR by a virtual quantity of 1 and by a host platform quantity of 0.1. Press the button Save to submit the TPM workflow to execute the HMC command.

6 Creation of LPAR or Virtual Server Virtual Server Template is used to specify the amount and types of resources desired for the creation of a virtual server or LPAR. Navigate in TPM UI to Inventory > Manage Templates > Virtual Server Templates to view the Power 5 template of Power5_micro_partition and the Power 4 template of pseries_partition. Click on right hand side button for action of Copy to copy into a new virtual server template for further modification. Power5_micro_partition was copied into test_micro_partition and then clicked on test_micro_partition to make further modifications of: For resource type of CPU, the Virtual Quantity seen by the operating system is 2 and the Host Platform Quantity of 0.2 is the physical CPU resources allocated. The following parameters and meaning for Power 5 at the LPAR level are: o cpu.max of 10 is the largest number of CPUs visible to the operating system. o cpu.max_proc_units of 2.0 is the maximum physical processor units. o cpu.min of 2 is the smallest number of CPUs visible to the operating system. o cpu.min_proc_units of 0.2 is the minimum physical processor units. For resource type of Memory, the Virtual Quantity and Host Platform Quantity must be the same value with 512 MB in this example. Parameters memory.max, memory.min defines the maximum and minimum physical memory. For resource type of Hard Disk, changed Host Platform Quantity to 30.0 GB and defined parameters of vio.server of todvios2 and vio.vg of clientsvg. A logical volume of 30.0 GB will be allocated from volume group of clientsvg from VIO server todvios2 and mapped to the LPAR created as a rootvg volume group. For resource type of NIC, defined parameter vio.vlan_ids with a value of 8 for the Virtual LAN (VLAN) ID. This is a virtual NIC with a resource group vnic. The pseries-server automation package documentation has more virtual server template parameters documented like cpu.sharing_mode, cpu.uncap_weight if the LPAR is to be capped or uncapped. The virtual server template test_micro_partition is shown here:

7 To allocate the virtual server or LPAR, navigate in TPM UI to Inventory -> Manage Inventory -> Computers. Then click on the managed system or host platform computer. Diagram Allocate Virtual Server shows Edit > Allocate a Virtual Server with input of Name of LPAR of mmaix6, host platform of TP SN10FB28C, template name of the virtual server template test_micro_partition. Press the button Save and monitor workflow submitted for successful execution. LPAR with be created in TPM as a computer. The TPM create virtual server workflow will check the allocation requests for host platform quantities against the available managed system resources. If not enough available, then an error message of: COPCOM053E The system cannot allocate n.n shares of resource name from the nnnn host platform. The HMC console will allow creation of a logical partition and will find out if not enough available resources when activating the LPAR. The LPAR name will be the TPM computer name. A DNS lookup of the TPM computer name for a LPAR with a single Network Interface Card (NIC) is done to define the network interface with the IP address. The manual definition of the network interface does not need to be done prior to install AIX image if the LPAR name is defined in DNS with a valid IP address. Allocate Virtual Server

8 5. Setup and Discovery of NIM If you need to define a new NIM server, the pseries and AIX Information Center has a topic "Configuring the NIM master and creating basic installation resources using SMIT" on how to setup a NIM server. A NIM server can be defined in TPM by: Install and configure SSH on the NIM server as documented in the NIM automation package documentation. The next step for Discover Computers using SSH will define a password credential for the SSH/SCP Service Access Point (SAP) so usage of RSA is optional. Discover the NIM server as a TPM computer by navigating in TPM UI to Inventory > Manage Discovery > Edit > Add Discovery Configuration for Discovery Computers using SSH. Define discovery parameters of the IP address of the NIM server and credentials for the root userid and password. Run the discovery configuration and monitor task for successful completion. Define an AIX OS software installation on the computer for the NIM server discovered. Navigate in TPM UI to Inventory -> Manage Inventory -> Computers and click on the NIM computer. Click on the Software tab and then Edit > Add Software Installation to define a AIX OS software installation with a software definition that matches the AIX release level. Define the TPM NIM boot server with the Add Boot Server wizard located in the TPM UI at Inventory > Infrastructure Management > Boot Servers > Edit > Add Boot Server Wizard. Select a boot server type of NIM and target of the NIM server. Monitor task for successful completion. An existing NIM server can have the mksysb images and NIM client or machines discovered in TPM by: Define a NIM discovery configuration by navigating in TPM UI to Inventory > Manage Discovery > Edit > Add Discovery Configuration for NIM Discovery. Define discovery parameters of NoServers to true and server to the name of the NIM boot server in TPM UI from Inventory > Infrastructure Management > Boot Servers. The discovery parameter of NoServers is set to true to not define NIM clients as TPM computers due to HMC Discovery discovered the LPARs as TPM computers. Run the NIM Discovery configuration and monitor task for successful completion. If you have standalone AIX servers, you could discover them as TPM computers with Discovery Computers using SSH. In TPM UI, Software Management > Manage Software Catalog > Images will show the AIX NIM mksysb images discovered from the NIM server. Diagram TPM Image shows a TPM AIX mksysb image with CPU hardware requirements for cpu.type and cpu.family. The target computer in TPM must have a CPU hardware resource with matching parameters to represent a pseries computer for the install image to start execution.

9 TPM Image There is a software stack associated with the image that contains a configuration template shown in diagram TPM Software Stack. The configuration template contains parameters to define which mksysb image with parameter NIM.mksysb parameter, NIM spot with parameter NIM.spot and a timeout parameter of GraceTime. The configuration template can be edited to add additional NIM parameters of: NIM.bid for NIM bos installation options. NIM.resolv_conf for content of /etc/resolv.conf. NIM.filesets for list of AIX filesets in installp or rpm format to install. NIM.lpp_source for the NIM lpp source. These and other NIM parameters are documented in the NIM automation package. TPM Software Stack

10 If a LPAR is powered down at the start of TPM install image, the HMC command lpar_netboot will be executed remotely from the NIM server to the HMC server to power up and network boot the LPAR. The RSA public key for the NIM server root password must be concatenated to the authorized_keys2 file of the HMC server userid hscroot. The steps for this are documented in the NIM automation package documentation. 6. Capture mksysb image to NIM server Discover the AIX server as a TPM computer to capture an image of by navigating in TPM UI to Inventory > Manage Discovery > Edit > Add Discovery Configuration for Discovery Computers using SSH. Define discovery parameters of the IP address of the AIX server and credentials for the root userid and password. Run the discovery configuration and monitor task for successful completion. Define an AIX OS software installation on the computer for the AIX server discovered. Navigate in TPM UI to Inventory -> Manage Inventory -> Computers and click on the AIX computer. Click on the Software tab and then Edit > Add Software Installation to define an AIX OS software installation with a software definition that matches the AIX release level. To capture an mksysb image to the NIM server: Navigate in TPM UI to Inventory > Manage Inventory > Computers and click on the AIX computer. On the General tab, click on Edit > Capture Image with the computer already selected as the source computer. Click Next. Select image type of Golden Master or Point-in-Time Snapshot and the NIM boot server to use to capture the image. Specify a name and description. The default image name is the os.name, os.version, os.servicepack of the OS software installation of the computer. A generated number is appended for uniqueness of the image name. You can choose to use the default image name or specify a unique name. Entering a description can help to choose which image to install. The NIM parameter of NIM.installPath must be specified and exist in a filesystem with sufficient free space. The other NIM parameters of NIM.bid, NIM.lpp_source, NIM.spot are optional parameters to specify values for. These NIM parameters are defined in the configuration template of the software stack associated with the image to be used for install image. If no NIM.spot is specified, then a NIM spot will be matched to the AIX release level of the NIM client. Click Next. Specify to execute the task now or enter a date and time that you want the task to start Click Next. Verify your choices on the Summary page. Click Finish. Monitor task for successful completion If you want to view the image that you have just captured, navigate to Software Management > Manage Software Catalog > Images and search for the image name. The TPM definition of Golden Master is a depersonalized boot device image that is used for deployment on multiple computers. For AIX mksysb, this means the golden master image install with have "RECOVER_DEVICES" stanza entry in the bosinst_data resource set to "no" or "Default" for no recovery of devices. The ODM configuration database is saved in the image. The device names and attributes from the ODM configuration database are not recreated. The TPM definition of Snapshot is an image that is used for restoring the original operating system. This type of image would be used to backup an operating system. For AIX mksysb, this means the snapshot image install will have "RECOVER_DEVICES" stanza entry in the bosinst_data resource will be set to "yes" for recovery of devices. The ODM configuration database is saved in the image. The device names and attributes from the ODM configuration database are recreated.

11 7. Definition of AIX Scripted Install image You can also define an image with a type of Scripted Install. This would be from AIX installation CDROM media with the configuration template parameters of NIM.lpp_source and NIM.spot. SSH filesets can also be installed. The NIM automation package documentation under heading To create a Scripted Install Image has further details on how to implement. 8. Install of NIM mksysb image to a powered down LPAR Navigate in TPM UI to Software Management > Manage Software Catalog > Images to search for the image to install. Click on the image and then Edit > Install Image. Under Select Computers, select the computer(s) to install the image. Optionally you can click on the button Advanced if you want to view and override the configuration template parameters for NIM. Click Submit and monitor the install image task. You can also install images from TPM UI navigation of Software Management > Install > Images.

12 The AIX NIM install image workflow will: Check if the NIM machine or client is defined to the NIM server. If not defined, will define. Execute the nim_install.sh script with the configuration template parameters for the nim bos_inst command on the NIM server. If the LPAR is not reachable via ping and NIM query command, then HMC command lpar_netboot is executed on the HMC server remotely from the NIM server to power up and network boot the LPAR. The state of the NIM client will be monitored for: o BOS installation has been enabled to start the installation. o If there is error information from the NIM client, this is displayed as workflow o log warning messages. When state is ready for a NIM operation or currently running to indicate that installation has completed. At the end of the install image workflow, the hostname command is executed every 60 seconds for 15 minutes to determine when the AIX OS is initialized. This is for support of software stack installs so that the next software stack entry will not start install until AIX OS is initialized. 9. Install of AIX software products There are three methods described below that you could use to install AIX software products. Software Product Install using NIM From TPM UI navigation of Inventory > Software Catalog > Software Products > Edit > Add Software Product, you can define AIX software products to install AIX filesets in installp or rpm format from the NIM server. This is documented further in the NIM automation package documentation under heading To install additional AIX software onto a NIM client with definition of configuration template parameters for NIM.lpp_source and NIM.filesets, NIM.installp_bundle or NIM.fix_bundle. NIM client filesets must be installed and the NIM client configured to communicate with NIM boot server. TPM computers have the NIM.masterID variable set for the NIM boot server to use. Simple Software Product Install using Hosting Environment The simple software product install is easier to define and perform native installs without developing a TPM automation package. The TPM Information Center under Software Distribution and Simple software product distribution describes: Storing the native install file or bundled file to extract in the TPM server local file repository. Defining a Software Product in the TPM software catalog. Defining a configuration template with choosing a operating system platform Hosting Environment definition to install a native AIX, Linux, Solaris or Windows package. Required definition of the install command. Optionally you can define the extraction of the bundled file, location of response file and license key file. Software Product Install using Software Pack Block Another method of installing AIX software products is to use Software Package Block (SPB) with a native AIX package defined in the SPB to install AIX filesets. SPB is a packaging format from Tivoli Configuration Manager (TCM) and can be used in TIO, TPM and TPM for Software. An SPB can be defined from the Software Package Editor that is launched from Software Management > Manage Software Catalog > Software Products > Edit > Launch SPE. Once a SPB is defined, it is saved into the TPM local file repository and appears as a software product in

13 the software catalog for installation. Installation of a SPB can only be done on computers with Tivoli Common Agent (TCA) installed that has a Software Installation Engine (SIE) subagent that handles the installation of SPBs. SPB installation can be done on Windows and UNIX computers if you want to use a common packaging and installation method in a multi-platform environment. SPB is the packaging format used when installing in the Scalable Distribution Infrastructure (SDI) environment with: Dynamic Content Delivery Server Depot servers in various geographical locations for file replication and download to reduce network latency and bandwidth usage for distribution and installation of software. Device Manager Federator servers in various geographical locations for processing jobs with software distribution and installation. The AIX software products are installed from Software Management > Install > Software Products. 10. Install of AIX software stacks Software stacks can be defined to install a group of software in a certain sequence. The software stack can have an AIX image as the first software object to install. To define a new software stack: 1. Navigate in TPM UI to Software Management > Manage Software Catalog > Software Stacks. 2. Click Edit and Add Software Stack. 3. Type a Name and a Description. Save the new software stack. 4. Click the name of the new software stack and then click Edit > Add Stack Entries. 5. Choose Software Stack and then select the software stack associated with the image stored on the NIM boot server. Click Next. 6. On the Configuration Template page, select the software stack template for the image. Click Next. 7. On the Customize Template page, make any required changes to the installation template values. Click Finish. The software stack is created. The software stack of the image is ordered to be installed first. 8. Select the software stack and then click Edit > Add Installable 9. In the Software Installable list, choose -iterator- and click Save. If you do not select - iterator-, you will receive an error message when you install the software stack. Tivoli Provisioning Manager will not recognize the computer as a match for the selected software. 10. Click Edit > Add Stack Entries. 11. In the Software Definition list, select Software Definition and then select a software definition from the list. You can also type a search string to find a software definition. You can also add a software stack or a software patch instead of a software definition. 12. On the Configuration Templates page, select the appropriate template. Click Next. 13. On the Customize Templates page, make the required changes to the template values. Click Finish. For any additional software that you want to add to the software stack, repeat steps 10 to 13. Add the software in the order that you want the software to be installed within the software stack. To install the software stack, navigate in the TPM UI to Software Management > Install > Software Stacks. Select your new software stack and the computer(s) that you want to install the software stack on. Click Submit. You can click Advanced to modify the values of the configuration templates before installing the software stack.

14