Académique Documents
Professionnel Documents
Culture Documents
html
unixwerk > AIX > Howtos > HMC Commandline June 11, 2013
unixwerk H o w t o u s e t h e H M C C o mm a n d l i n e
This documents contains the most important HMC commands. It covers both, the old power4 commands (up to HMC Version 3) and the new power5 style commands (HMC Version 4-6). A lot of
nice commands still available for version 3 (power4) are removed from newer releases. One example of these nice commands is lslpars and it's not available for HMC version 4 and higher.
AIX The real reason behind it is that IBM wants to force us to use the web based tools wsm and WebSM or the new HMC browser GUI. This documents helps you to survive with the HMC commands
in case working with the web based tools is not feasible.
BSD In the examples below we call a whole power4 or power5 frame (aka Managed System) pserver. We call an LPAR mylpar. If an example output shows more than one LPAR name we
enumerate it. LPAR Profiles are shown as myprofile. You have to replace these names with your object names.
HP-UX
If you use power6 systems, you need the new HMC version7. Although the GUI has changed from wsm to a browser based service, the commandline remains compatible. You can just use the
Linux power5 examples for power6 and power7. However, additional features have been implemented.
Solaris
Others Contents
LPAR Configuation
1. Change an LPAR's Name
2. Rename a Managed System
3. DLPAR: Increase the Number of Processing Units of an LPAR
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.
hscroot@hmc> lshmc -n
power4 + power5/6/7:
It's just the same as you would expect from the UNIX command df.
1. LPAR Status
That's how you get an overview of all systems controlled by your HMC:
power4:
hscroot@hmc> lslpars
power5/6/7:
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:
Example:
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
power5/6/7:
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 type
power5/6/7:
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.
power5/6/7:
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:
power5/6/7:
power5/6/7:
5. Virtual Console
power4 + power5/6/7:
If your system is running in FullSystemPartition-Mode you connect with a command like this:
power4:
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:
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
----------------------------------------------------------
Partitions On Managed System: pserver1
----------------------------------------------------------
1) mylpar1 Running
2) mylpar2 Running
3) mylpar3 Running
4) mylpar4 Running
5) mylpar5 Running
Just enter a number and you will be connected to the console of the corresponding LPAR.
6. Activation of an LPAR
power4:
power5/6/7:
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:
power5/6/7:
With new HMCs a special profile is not any longer needed. The profile's boot mode can be overwirtten with -b:
The same way the LPAR can be bootet into the Open Firmware prompt (Bootmode: 'of'):
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:
LPAR Conguration
power5/6/7:
We check and see that the name of LPAR 3 indeed has changed to mylpar1:
This would change the name of the manages system pserver to pserver1:
power5/6/7:
power5/6/7:
HMC Version 7
HMC Version 7
You can also list the status of more than one LPAR in one go:
HMC Version 7