HMC Management
1. HMC Version
hscroot@hmc> lshmc -V
Version: 3
Release: 3.2
HMC Build level 20040827.1
power4 HMCs could never show a version higher 3.x - HMC version 4.x and higher are only for power5 systems. Power6 systems need HMCs version 7.x.
2. Network configuration of the HMC
hscroot@hmc> lshmc -n
3. Reboot the HMC
power4 + power5/6/7:
hscroot@hmc> hmcshutdown -t now -r
4. How to change the HMC password (of user hscroot)
power4 + power5/6/7:
hscroot@hmc> chhmcusr -u hscroot -t passwd
Enter the new password:
Retype the new password:
5. Show Available Filesystem Space
power5/6/7:
hscroot@hmc> monhmc -r disk -n 0
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 16121184 4958484 10343788 33% /
udev 517300 156 517144 1% /dev
/dev/sda3 6040320 1341736 4391744 24% /var
/dev/sda7 8056524 154132 7493140 3% /dump
/dev/sda8 38669964 203056 36502564 1% /extra
LPAR Management: Status Information
1. LPAR Status
That's how you get an overview of all systems controlled by your HMC:
power4:
hscroot@hmc> lslpars
power5/6/7:
hscroot@hmc> lssyscfg -r sys -F name:serial_num:statepserver1:656D24A:Operatingpserver2:656FFFF:Operating
The format string 'lpar_id:name:serial_num:state' also tells you the serial number of the systems. You can omit the field 'serial_num' if you don't need to know.
However, for every system from the list above you get the LPAR overview as shown below:
However, for every system from the list above you get the LPAR overview as shown below:
hscroot@hmc> lssyscfg -mpserver-r lpar -F name:state
Example:
hscroot@hmc> lssyscfg -mpserver1-r lpar -F name:statemylpar1:Runningmylpar2:Runningmylpar3:Not Activated
Don't know where to start? Find the managed system to an LPAR with a query:
hscroot@hmc> for m in $(lssyscfg -r sys -F name); do echo $m ; lssyscfg -r lpar -m $m -F name:state ; done
2. Show Status and LED/LCD Display of an LPAR
power4:
hscroot@hmc> lssyscfg -r lpar -mpserver-nmylpar
power5/6/7:
hscroot@hmc> lsrefcode -mpserver-r lpar --filter "lpar_names=mylpar" -F lpar_name:refcode
You can even see the history of LED codes. Just use
-n <NUM> for the last NUM codes. For example, if you want to see the last 5 LED codes of an LPAR typehscroot@hmc> lsrefcode -mpserver-r lpar --filter "lpar_names=mylpar" -n 5 -F lpar_name:refcode
mylpar:
mylpar:0c33
mylpar:
mylpar:0539
mylpar:0538
... and for the status LEDs:
hscroot@hmc> lsled -mpserver-r sa -t virtuallpar --filter ""lpar_names=mylpar""
3. Show Status and LED/LCD Display of a Systems Running in FullPartitionMode
power4:
hscroot@hmc> lssyscfg -r sys -npserver
4. Overview LPAR IDs
power5/6/7:
hscroot@hmc> lssyscfg -r lpar -mpserver-F lpar_id:name:serial_num:state | sort -n
1:vioserver1:Running
2:vioserver2:Running
3:mylpar1:Not Activated
4:mylpar2:Running
5:mylpar3:Running
6:mylpar4:Running
7:mylpar5:Running
8:mylpar6:Running
9:mylpar7:Running
10:mylpar8:Not Activated
5. Overview Connection State
Are all service processors connected to my HMC?
power5/6/7:
hscroot@hmc> lssysconn -r all -F type_model_serial_num:ipaddr:state | sort
9117-570*65AE18C:172.16.255.253:Connected
9117-570*65AE18C:172.16.254.255:Connected
9117-570*65AE2AC:172.16.255.254:Connected
9117-570*65AE2AC:172.16.254.254:Connected
9117-570*650D70D:172.16.255.252:Connected
9117-570*650D70D:172.16.253.255:Connected
9117-570*650D71D:172.16.254.253:Connected
9117-570*650D71D:172.16.255.251:Connected
9131-52A*065F7BB:172.16.253.254:Connected
9131-52A*065F8BA:172.16.254.252:Connected
The link to the name of the managed system is the serial number - not the IP address! The IP addresses listed above are mounted on the service processor's private NIC and managed by the integrated DHCP server of the HMC.
6. Show a List of All I/O Adapters
The command below will show a list of all adapters physically plugged into a Managed System:
power5/6/7:
hscroot@hmc> lshwres -r io -mpserver--rsubtype slot --filter -F lpar_name:drc_name:description
null:U78C0.001.DBJC357-P2-C8-T5:Universal Serial Bus UHC Spec
mylpar1:U78C0.001.DBJC357-P2-C1:Fibre Channel Serial Bus
null:U78C0.001.DBJC357-P2-C2:Fibre Channel Serial Bus
vios2:U78C0.001.DBJC357-P2-T3:RAID Controller
vios2:U78C0.001.DBJC357-P2-C8-T7:Generic XT-Compatable Serial Controller
vios2:U78C0.001.DBJC357-P2-C5:Fibre Channel Serial Bus
vios2:U78C0.001.DBJC357-P2-C6:Ethernet controller
vios2:U78C0.001.DBJC357-P2-C9-T2:PCI-E SAS Controller
vios2:U78C0.001.DBJC357-P2-C9-T1:PCI-E SAS Controller
null:U78C0.001.DBJC373-P2-C8-T5:Universal Serial Bus UHC Spec
mylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Bus
null:U78C0.001.DBJC373-P2-C2:Fibre Channel Serial Bus
vios1:U78C0.001.DBJC373-P2-T3:RAID Controller
vios1:U78C0.001.DBJC373-P2-C8-T7:Generic XT-Compatable Serial Controller
vios1:U78C0.001.DBJC373-P2-C5:Fibre Channel Serial Bus
vios1:U78C0.001.DBJC373-P2-C6:Ethernet controller
vios1:U78C0.001.DBJC373-P2-C9-T2:PCI-E SAS Controller
vios1:U78C0.001.DBJC373-P2-C9-T1:PCI-E SAS Controller
A leading "
none" indicates that the adapter is not assigned to an LPAR. To show a list of all I/O adapters owned by a specific LPAR use the "--filter" modifier:power5/6/7:
hscroot@hmc> lshwres -r io -mpserver--rsubtype slot -F lpar_name:drc_name:description --filter "lpar_names=mylpar1"
mylpar1:U78C0.001.DBJC357-P2-C1:Fibre Channel Serial Bus
mylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Bus
7. Overview DLPAR status
power5/6/7:
hscroot@hmc> lspartition -dlpar
<#0> Partition:<6*9117-MMB*656D24A, mylpar1.unixwerk.de, 111.111.15.66>
Active:<0>, OS:<AIX, 5.3, 5300-09-08-1036>, DCaps:<0x0>, CmdCaps:<0x0, 0x0>, PinnedMem:<512>
<#1> Partition:<2*9117-MMB*656D24A, vios1.unixwerk.de, 111.111.15.65>
Active:<1>, OS:<AIX, 6.1, 6100-06-00-0000>, DCaps:<0x4f9f>, CmdCaps:<0x1b, 0x1b>, PinnedMem:<520>
<#2> Partition:<1*9117-MMB*656D24A, vios2.unixwerk.de, 111.111.15.64>
Active:<1>, OS:<AIX, 6.1, 6100-06-00-0000>, DCaps:<0x4f9f>, CmdCaps:<0x1b, 0x1b>, PinnedMem:<518>
<#3> Partition:<3*9117-570*656FFFF, mylpar2.unixwerk.de, 111.111.226.4>
Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<1707>
<#4> Partition:<1*9117-570*656FFFF, mylpar3.unixwerk.de, 111.111.226.2>
Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<884>
<#5> Partition:<1*9133-55A*650D71D, mylpar7.unixwerk.de, 111.111.0.26>
Active:<1>, OS:<AIX, 5.3, 5300-09-03-0918>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<406>
<#6> Partition:<4*9117-570*656FFFF, mylpar4.unixwerk.de, 111.111.226.5>
Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<967>
LPAR Management: Operations
1. Soft Reset of an LPAR
power4:
hscroot@hmc> chsysstate -mpserver-r lpar -nmylpar-o reset
power5/6/7:
hscroot@hmc> chsysstate -r lpar -mpserver-o shutdown -nmylpar
2. Soft Reset of a System Running in FullPartitionMode
power4:
hscroot@hmc> chsysstate -npserver-r sys -o reset
3. Hard Reset of an LPAR
power4:
hscroot@hmc> chsysstate -mpserver-r lpar -nmylpar-o off
power5/6/7:
hscroot@hmc> chsysstate -r lpar -m pseries -o shutdown -nmylpar--immed
4. Hard Reset of a System Running in FullPartitionMode
power4:
hscroot@hmc> chsysstate -npserver-r sys -o off
5. Virtual Console
That's how you get a connection to an LPAR's serial console:
power4 + power5/6/7:
hscroot@hmc> mkvterm -mpserver-pmylpar
If your system is running in FullSystemPartition-Mode you connect with a command like this:
power4:
hscroot@hmc> mkvterm -mpserver
You can escape from the console connection by typing ~~. (twice tilde followed by a dot)
If you cannot connect to the serial console and you get an error message instead:
All available virtual terminal sessions have been opened and are in use.
To force a new open session, perform a Close Terminal Session operation
which frees up the session.
there is still another active connection to this console. You can close this connection with:
power4 + power5/6/7:
hscroot@hmc> rmvterm -mpserver-pmylpar
If you're not sure which managed system belongs to an LPAR you could walk through the vtmenu:
hscroot@hmc> vtmenu
Retrieving name of managed system(s) . . .
----------------------------------------------------------
Managed Systems:
----------------------------------------------------------
1) pserver1
2) pserver2
3) pserver3
Enter Number of Managed System. (q to quit): 1
----------------------------------------------------------
Partitions On Managed System: pserver1
----------------------------------------------------------
1) mylpar1 Running
2) mylpar2 Running
3) mylpar3 Running
4) mylpar4 Running
5) mylpar5 Running
Enter Number of Running Partition (q to quit):
6. Activation of an LPAR
power4:
hscroot@hmc> chsysstate -r lpar -mpserver-o on [ -fmyprofile] -nmylpar
power5/6/7:
hscroot@hmc> chsysstate -r lpar -mpserver-o on -fmyprofile-nmylpar
7. How to Boot an LPAR into SMS Menu
power4:
You have to create an additional profile. In this profile set the boot mode to 'sms'. We call the profile
mysmsprofile. Then start the LPAR with this profile:hscroot@hmc> chsysstate -r lpar -mpserver-o on -fmysmsprofile-nmylpar
power5/6/7:
With new HMCs a special profile is not any longer needed. The profile's boot mode can be overwirtten with
-b:hscroot@hmc> chsysstate -r lpar -mpserver-o on -fmyprofile-b sms -nmylpar
The same way the LPAR can be bootet into the Open Firmware prompt (Bootmode: 'of'):
hscroot@hmc> chsysstate -r lpar -mpserver-o on -fmyprofile-b of -nmylpar
8. How to Power on a System Running in FullPartitionMode
power4:
hscroot@hmc> chsysstate -o on -r sys -npserver-c full
9. Bring the key switch to position NORMAL
This might be necessary on some power5 HMCs when an LPAR does not properly boot after issuing the power on command above. You might see a message like this:
0514-440 cfgcon: failed to create log file: check path name, permissions, and available space
When seeing this you can only access diag mode or boot the LPAR in singleuser mode. This command sets the key switch back to normal position:
power5/6/7:
hscroot@hmc> chsysstate -r lpar -o chkey -k norm -nmylpar-mpserver
LPAR Configuration
1. Change an LPAR's Name
Let's say we have these five LPARs defined on a managed system:
hscroot@hmc> lssyscfg -r lpar -mpserver-F lpar_id:name:state
1:vios1:Running
2:vios2:Running
3:barney:Running
4:mylpar2:Running
5:mylpar3:Running
Now we want to change the name of LPAR 3 from barney to mylpar1:
power5/6/7:
hscroot@hmc> chsyscfg -r lpar -mpserver-i "name=barney,new_name=mylpar1"
We check and see that the name of LPAR 3 indeed has changed to mylpar1:
hscroot@hmc> lssyscfg -r lpar -mpserver-F lpar_id:name:state
1:vios1:Running
2:vios2:Running
3:mylpar1:Running
4:mylpar2:Running
5:mylpar3:Running
2. Rename a Managed System
This would change the name of the manages system pserver to pserver1:
power5/6/7:
hscroot@hmc> chsyscfg -r sys -mpserver-i "new_name=pserver1"
3. DLPAR: Increase the Number of Processing Units of an LPAR
To assign 8 additonal processing units to an LPAR run the following command:
power5/6/7:
hscroot@hmc> chhwres -r proc -mpserver-o a -pmylpar--procunits 8
cool like it
ReplyDelete