LPAR Creation (new)

High Level Overview

  1. Request ip addresses
  2. Get lpar added to abacus / assyst (so that accredited change can be raised with corect name)
  3. Raise accredited change (ACHG0038) specifying 2 day build time.
  4. Log in to appropriate HMC with a browser https://hmc1.brm.pri for Laindon (or hmc2 or hmc3 for West Malling), log in as hscroot and the password.
  5. Create Profile on appropriate P595, remember the LPAR Partition number. Specify “Normal” as profile name, specify memory, and cpu. Create 2 virtual scsi adapters and one virtual ethernet. The scsi adapters will need changing later on after adding a virtual scsi host adapter to VIO.
  6. Define the LPAR on the NIM server
  7. Create rootvg and rootvgm disks on SVC. Map through to client using mapvclient.ksh. Do this process one disk at a time!!!(information on creating all disks see create-lun-filesystems sections 1-3)
  8. Install OS
  9. Map remaining vdisks throught to the client
  10. create filesystems
  11. Tidy up files containing information from the cloned LPAR
  12. Uninstall / Install TIVOLI agents

Details

Define LPAR Profile on HMC

Create Virtual adapter on VIO server

Define LPAR on NIM Server

Create LUN on SVC

Start install of OS from HMC terminal

Create and map through the remaining vdisks

Create filesystems

Tidy up prior to adding front facing ip

Uninstall / install Tivoli monitoring agents

Add User community vlan interface

In the HMC interface add another Virtual Ethernet Interface to the Profile, connected to the appropriate VLAN. Also add this to the running profile with the DLPAR option.

On the build LPAR, run cfgmgr to discover the new interface, probably en1. Add the appripriate info for this interface in smitty. It is likely that a secondary interface has been defined for user services to use, add thei in /etc/rc.net:-

bash-3.00# cat /etc/rc.net
....cut....
/usr/sbin/ifconfig en1 inet 10.84.16.124 netmask 255.255.240.0 alias 1>/dev/null 2>&1

Finishing off tasks

Add Cross-site static routes

Delete NMON data cloned from source system

Delete nmon data cloned from source system in the /nmon/nmon_data directory.

Disable Metron

Comment out the entries in the metron users crontab.

For production the new system will need a new unique id before metron can be re-enabled.

Test ssytems should not be enabled for metron.

TSM Connectivity

TSM, if this LPAR is a clone of a mksysb image, ensure that you log in to the original machine to re-establish tsm connectivity.

Tivoli monitoring and Netcool Omnibus Build Actions

Problems

1. Using bare hostname instead of hostname-gbe

2. There is no NIM object named “xxxxx.image”

3. Using the wrong ipaddress for the client, ping may ping existing server.

 
aix/aix_lparcreate.txt · Last modified: 06/04/2022 08:14 by andrew