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.
If you use power6 systems, you need the new HMC version7. Although the GUI has changed from wsm to a browser based service, the commandlineremains compatible. You can just use the power5 examples for power6 and power7. However, additional features have been implemented.
hscroot@hmc> lshmc -V Version: 3 Release: 3.2HMC 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:
hscroot@hmc> hmcshutdown -t now -r
power4 + power5/6/7:
hscroot@hmc> chhmcusr -u hscroot -t passwdEnter the new password:Retype the new password:
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"
power5/6/7:
hscroot@hmc> monhmc -r disk -n 0Filesystem 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.
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:
hscroot@hmc> lssyscfg -m pserver
-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 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===pserver1
===1:mylpar1
:Running2:mylpar2
:Running3:mylpar3
:Not Activated===pserver2
===2:mylpar12
:Running3:mylpar13
:Running
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 type
hscroot@hmc> lsrefcode -mpserver
-r lpar --filter "lpar_names=mylpar
" -n 5 -F lpar_name:refcodemylpar:mylpar:0c33mylpar:mylpar:0539mylpar:0538
... and for the status LEDs:
hscroot@hmc> lsled -mpserver
-r sa -t virtuallpar --filter ""lpar_names=mylpar
""
power4:
hscroot@hmc> lssyscfg -r sys -n pserver
power5/6/7:
hscroot@hmc> lssyscfg -r lpar -mpserver
-F lpar_id:name:serial_num:state | sort -n1:vioserver1
:Running2:vioserver2
:Running3:mylpar1
:Not Activated4:mylpar2
:Running5:mylpar3
:Running6:mylpar4
:Running7:mylpar5
:Running8:mylpar6
:Running9:mylpar7
:Running10:mylpar8
:Not Activated
Are all service processors connected to my HMC?
power5/6/7:
hscroot@hmc> lssysconn -r all -F type_model_serial_num:ipaddr:state | sort9117-570*65AE18C:172.16.255.253:Connected9117-570*65AE18C:172.16.254.255:Connected9117-570*65AE2AC:172.16.255.254:Connected9117-570*65AE2AC:172.16.254.254:Connected9117-570*650D70D:172.16.255.252:Connected9117-570*650D70D:172.16.253.255:Connected9117-570*650D71D:172.16.254.253:Connected9117-570*650D71D:172.16.255.251:Connected9131-52A*065F7BB:172.16.253.254:Connected9131-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 managedby the integrated DHCP server of the HMC.
The command below will show a list of all adapters physically plugged into a Managed System:
power5/6/7:
hscroot@hmc> lshwres -r io -m pserver
--rsubtype slot --filter -F lpar_name:drc_name:descriptionnull:U78C0.001.DBJC357-P2-C8-T5:Universal Serial Bus UHC Specmylpar1:U78C0.001.DBJC357-P2-C1:Fibre Channel Serial Busnull:U78C0.001.DBJC357-P2-C2:Fibre Channel Serial Busvios2:U78C0.001.DBJC357-P2-T3:RAID Controllervios2:U78C0.001.DBJC357-P2-C8-T7:Generic XT-Compatable Serial Controllervios2:U78C0.001.DBJC357-P2-C5:Fibre Channel Serial Busvios2:U78C0.001.DBJC357-P2-C6:Ethernet controllervios2:U78C0.001.DBJC357-P2-C9-T2:PCI-E SAS Controllervios2:U78C0.001.DBJC357-P2-C9-T1:PCI-E SAS Controllernull:U78C0.001.DBJC373-P2-C8-T5:Universal Serial Bus UHC Specmylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Busnull:U78C0.001.DBJC373-P2-C2:Fibre Channel Serial Busvios1:U78C0.001.DBJC373-P2-T3:RAID Controllervios1:U78C0.001.DBJC373-P2-C8-T7:Generic XT-Compatable Serial Controllervios1:U78C0.001.DBJC373-P2-C5:Fibre Channel Serial Busvios1:U78C0.001.DBJC373-P2-C6:Ethernet controllervios1:U78C0.001.DBJC373-P2-C9-T2:PCI-E SAS Controllervios1: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 aspecific 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 Busmylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Bus
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>
A value <1> for Active: should be fine.
power4:
hscroot@hmc> chsysstate -mpserver
-r lpar -nmylpar
-o reset
power5/6/7:
hscroot@hmc> chsysstate -r lpar -mpserver
-o shutdown -nmylpar
power4:
hscroot@hmc> chsysstate -n pserver
-r sys -o reset
power4:
hscroot@hmc> chsysstate -mpserver
-r lpar -nmylpar
-o off
power5/6/7:
hscroot@hmc> chsysstate -r lpar -m pseries -o shutdown -n mylpar
--immed
power4:
hscroot@hmc> chsysstate -n pserver
-r sys -o off
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 -m pserver
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 operationwhich 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):
Just enter a number and you will be connected to the console of the corresponding 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
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
power4:
hscroot@hmc> chsysstate -o on -r sys -n pserver
-c full
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
Let's say we have these five LPARs defined on a managed system:
hscroot@hmc> lssyscfg -r lpar -m pserver
-F lpar_id:name:state1:vios1:Running2:vios2:Running3:barney:Running4:mylpar2:Running5:mylpar3:Running
Now we want to change the name of LPAR 3 from barney to mylpar1:
power5/6/7:
hscroot@hmc> chsyscfg -r lpar -m pserver
-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 -m pserver
-F lpar_id:name:state1:vios1:Running2:vios2:Running3:mylpar1:Running4:mylpar2:Running5:mylpar3:Running
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
"
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
HMC Version 7 can run operations on Virtual I/O Servers.
The below command would login all virtual adapters of the LPAR with ID 12 to the SAN:
HMC Version 7
hscroot@hmc> chnportlogin -o login -mpserver
--id12
e.g. for an LPAR with ID 12, type
HMC Version 7
hscroot@hmc> lsnportlogin -mpserver
--filter "lpar_ids=12
"lpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=51,wwpn=c050726660a0002c,wwpn_status=1,logged_in=vios,wwpn_status_reason=nulllpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=51,wwpn=c050726660a0002d,wwpn_status=1,logged_in=vios,wwpn_status_reason=nulllpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=52,wwpn=c050726660a0002e,wwpn_status=1,logged_in=vios,wwpn_status_reason=nulllpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=52,wwpn=c050726660a0002f,wwpn_status=1,logged_in=vios,wwpn_status_reason=null
You can also list the status of more than one LPAR in one go:
HMC Version 7
hscroot@hmc> lsnportlogin -mpserver
--filter "\"lpar_ids=12
,13
\""
HMC Version 7
hscroot@hmc> chnportlogin -o logout -mpserver
--id12
联系客服