How to use the HMC Commandline
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.
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.
In the examples below we call a whole power4 or power5 frame (aka Managed System) 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 power5 examples for power6 and power7. However, additional features have been implemented.
ContentsHMC Management
LPAR Management: Status Information
LPAR Management: Operations
LPAR Configuation
Operations in an virtualized environment
HMC Management1. 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 HMCpower4 + 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. How to add an SSH key for remote access
power5/6/7: hscroot@hmc> mkauthkeys -a "public key"Use the public key found in the users .ssh directory for public key (i.e. the contents of the file ~/.ssh/id_rsa.pub).
power5/6/7: hscroot@hmc> mkauthkeys -u user -a "public key"
6. Show Available Filesystem Spacepower5/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 It's just the same as you would expect from the UNIX command df. LPAR Management: Status Information1. LPAR StatusThat'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:state
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.
hscroot@hmc> lssyscfg -m
Example:
hscroot@hmc> lssyscfg -m Don't know where to start? Find all managed systems and LPARs with a query:
hscroot@hmc> for m in $(lssyscfg -r sys -F name); do printf "\n=== $m ===\n" ; lssyscfg -r lpar -m $m -F lpar_id:name:state | sort -n ; done ===
2. Show Status and LED/LCD Display of an LPARpower4: hscroot@hmc> lssyscfg -r lpar -m power5/6/7: hscroot@hmc> lsrefcode -m
You can even see the history of LED codes. Just use hscroot@hmc> lsrefcode -m ... and for the status LEDs: hscroot@hmc> lsled -m
3. Show Status and LED/LCD Display of a Systems Running in FullPartitionModepower4: hscroot@hmc> lssyscfg -r sys -n
4. Overview LPAR IDspower5/6/7: hscroot@hmc> lssyscfg -r lpar -m
5. Overview Connection StateAre 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 AdaptersThe command below will show a list of all adapters physically plugged into a Managed System: power5/6/7: hscroot@hmc> lshwres -r io -m
A leading " power5/6/7: hscroot@hmc> lshwres -r io -m
7. Overview DLPAR statuspower5/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> A value <1> for Active: should be fine. LPAR Management: Operations1. Soft Reset of an LPARpower4: hscroot@hmc> chsysstate -m power5/6/7: hscroot@hmc> chsysstate -r lpar -m
2. Soft Reset of a System Running in FullPartitionModepower4: hscroot@hmc> chsysstate -n
3. Hard Reset of an LPARpower4: hscroot@hmc> chsysstate -m power5/6/7: hscroot@hmc> chsysstate -r lpar -m pseries -o shutdown -n
4. Hard Reset of a System Running in FullPartitionModepower4: hscroot@hmc> chsysstate -n
5. Virtual ConsoleThat's how you get a connection to an LPAR's serial console: power4 + power5/6/7: hscroot@hmc> mkvterm -m If your system is running in FullSystemPartition-Mode you connect with a command like this: power4: hscroot@hmc> mkvterm -m 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 -m 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): Just enter a number and you will be connected to the console of the corresponding LPAR. 6. Activation of an LPARpower4: hscroot@hmc> chsysstate -r lpar -m power5/6/7: hscroot@hmc> chsysstate -r lpar -m
7. How to Boot an LPAR into SMS Menupower4:
You have to create an additional profile. In this profile set the boot mode to 'sms'. We call the profile hscroot@hmc> chsysstate -r lpar -m power5/6/7: With new HMCs a special profile is not any longer needed. The profile's boot mode can be overwirtten with
hscroot@hmc> chsysstate -r lpar -m The same way the LPAR can be bootet into the Open Firmware prompt (Bootmode: 'of'):
hscroot@hmc> chsysstate -r lpar -m
8. How to Power on a System Running in FullPartitionModepower4: hscroot@hmc> chsysstate -o on -r sys -n
9. Bring the key switch to position NORMALThis 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 -n
LPAR Configuration1. Change an LPAR's NameLet's say we have these five LPARs defined on a managed system:
hscroot@hmc> lssyscfg -r lpar -m
Now we want to change the name of LPAR 3 from barney to mylpar1: power5/6/7: hscroot@hmc> chsyscfg -r lpar -m
We check and see that the name of LPAR 3 indeed has changed to mylpar1: hscroot@hmc> lssyscfg -r lpar -m
2. Rename a Managed SystemThis would change the name of the manages system pserver to pserver1: power5/6/7: hscroot@hmc> chsyscfg -r sys -m 3. DLPAR: Increase the Number of Processing Units of an LPARTo assign 8 additonal processing units to an LPAR run the following command: power5/6/7: hscroot@hmc> chhwres -r proc -m
Operationen in einer virtualisierten UmgebungHMC Version 7 can run operations on Virtual I/O Servers. 1. Make virtual WWPNs visible to the SANThe below command would login all virtual adapters of the LPAR with ID 12 to the SAN: HMC Version 7 hscroot@hmc> chnportlogin -o login -m 2. Show all virtual WWPNs assigned to an LPARe.g. for an LPAR with ID 12, type HMC Version 7 hscroot@hmc> lsnportlogin -m You can also list the status of more than one LPAR in one go: HMC Version 7 hscroot@hmc> lsnportlogin -m
3. Logout virtual WWPNs from the SANHMC Version 7 hscroot@hmc> chnportlogin -o logout -m
|
|