To configure the HMC, do the following steps:

HMC
To configure the HMC, do the following steps:

1. Turn on the HMC by pressing the power button.

2. Wait for the HMC to automatically select the default language and locale preference.

3. Accept the HMC license agreements. If you decline the HMC license agreements, you cannot complete the HMC configuration.

4. Click Log on and launch the Hardware Management Console web application.

5. Log in to the HMC:

ID: hscroot

Password: abc123

The Guided Setup wizard opens.

6. Click OK on the Guided Setup entry window.

7. Complete the steps in the Guided Setup wizard. Click Yes to continue and complete the steps in the Connectivity and Call-Home Servers wizard.

8. On the Summary window, click Finish.

9. If you have not connected the Ethernet crossover cable to your managed system, do so now and power on the managed server.

10. In the HMC navigation area, click Service Management.

11. In the contents area, click Authorize User. The Authorize User window opens.

12. Enter your IBM® ID in the field and click OK.

Creating LPAR using SSH

Get the configuration data from existing LPAR

If you already have LPARs created you can use this command to get their configuration which can be reused as template:

lssyscfg -r prof -m SERVERNAME --filter "lpar_ids=X, profile_names=normal"

Create new LPAR using command line

Here is an example, for more information see '''man mksyscfg'''

mksyscfg -r lpar -m MACHINE -i name=LPARNAME, profile_name=normal, lpar_env=aixlinux, shared_proc_pool_util_auth=1, min_mem=512, desired_mem=2048, max_mem=4096, proc_mode=shared, min_proc_units=0.2, desired_proc_units=0.5, max_proc_units=2.0, min_procs=1, desired_procs=2, max_procs=2, sharing_mode=uncap, uncap_weight=128,boot_mode=norm, conn_monitoring=1, shared_proc_pool_util_auth=1

Create more LPARs using configuration file

If you want to create more LPARS at once you can use a configuration file and provide it as input for mksyscfg.

Here is an example for 3 LPARs, each definition starting at new line:

name=LPAR1,profile_name=normal,lpar_env=aixlinux,all_resources=0,min_mem=1024,desired_mem=9216,max_mem=9216,proc_mode=shared,min_proc_units=0.3,desired_proc_units=1.0,max_proc_units=3.0,min_procs=1,desired_procs=3,max_procs=3,sharing_mode=uncap,uncap_weight=128,lpar_io_pool_ids=none,max_virtual_slots=10,"virtual_scsi_adapters=6/client/4/vio1a/11/1,7/client/9/vio2a/11/1","virtual_eth_adapters=4/0/3//0/1,5/0/4//0/1",boot_mode=norm,conn_monitoring=1,auto_start=0,power_ctrl_lpar_ids=none,work_group_id=none,shared_proc_pool_util_auth=1
name=LPAR2,profile_name=normal,lpar_env=aixlinux,all_resources=0,min_mem=1024,desired_mem=9216,max_mem=9216,proc_mode=shared,min_proc_units=0.3,desired_proc_units=1.0,max_proc_units=3.0,min_procs=1,desired_procs=3,max_procs=3,sharing_mode=uncap,uncap_weight=128,lpar_io_pool_ids=none,max_virtual_slots=10,"virtual_scsi_adapters=6/client/4/vio1a/12/1,7/client/9/vio2a/12/1","virtual_eth_adapters=4/0/3//0/1,5/0/4//0/1",boot_mode=norm,conn_monitoring=1,auto_start=0,power_ctrl_lpar_ids=none,work_group_id=none,shared_proc_pool_util_auth=1
name=LPAR3,profile_name=normal,lpar_env=aixlinux,all_resources=0,min_mem=1024,desired_mem=15360,max_mem=15360,proc_mode=shared,min_proc_units=0.4,desired_proc_units=1.0,max_proc_units=4.0,min_procs=1,desired_procs=4,max_procs=4,sharing_mode=uncap,uncap_weight=128,lpar_io_pool_ids=none,max_virtual_slots=10,"virtual_scsi_adapters=6/client/4/vio1a/13/1,7/client/9/vio2a/13/1","virtual_eth_adapters=4/0/3//0/1,5/0/4//0/1",boot_mode=norm,conn_monitoring=1,auto_start=0,power_ctrl_lpar_ids=none,work_group_id=none,shared_proc_pool_util_auth=1

Copy this file to HMC and run:
mksyscfg -r lpar -m SERVERNAME -f /tmp/profiles.txt

To check the HMC version
lshmc -V

Eg:
Release: 3
Version: 2.5
HMC Build level 20031020.1

To check the HMC vital product data information
lshmc -v

Eg:
Vital Product Data Information:
*FC ????????
*VC 20.0
*N2 Mon Aug 20 13:12:39 BST 2007
*FC ????????
*DS pSeries Hardware Management Console
*TM eserver xSeries 335 -[7315CR2]-
*SE 651BABA
*MN IBM
*PN Unknow
*SZ 1055932416
*OS Linux 2.4.20-19.7
*NA 10.35.0.135
*FC ????????
*DS Platform Firmware
*RM R3V2.5

To check the HMC network configurations:
lshmc -n

To List last 2 days console log details
lssvcevents -t console -d 2

HMC Hints:
Power 4 HMC Commands


To view partition state:
get_partition_state

To pop a hung partiton into the debugger (aka 'soft reset'):
reset_partition -m -p -t soft

To force a reboot of a hung system (aka 'hard reset'):
reset_partition -m -p -t hard

To start a partition:
start_partition -p -f -m

To get a listing of boot profiles:
query_profile_names -m -p

Power 5 HMC Commands

To see system state for a system or the partitions on a system:
lssyscfg -r sys -m
lssyscfg -r lpar -m

To just see names and state:
lssyscfg -r lpar -m -F name,state --header

To power on an lpar with a profile:
chsysstate -m -o on -r lpar -n -f
i.e. for example:
chsysstate -m alpha -o on -r lpar -n alpha-lp1 -f default

To power on a whole machine (CEC):
chsysstate -m alpha -o on -r sys

Etc. chsysstate, lssyscfg and other commands have good explanations if they're run without arguments.

Issuing a 'soft reset', to push a hung machine into KDB/XMON, is not obvious. The magic incantation is:
chsysstate -r lpar -m -n -o dumprestart

To issue a 'hard reset', to turn off a partition, no matter what:
chsysstate -r lpar -m -n -o shutdown --immed --restart

To add one virtual CPU: (note these use -p instead of -n for the partition name)
chhwres -r proc -m -p -o a --procs 1

To add one-tenth of a cpu processing entitlement:
chhwres -r proc -m -p --procunits 0.1