Command line syntax


monhmc -r mem -n 0
monhmc -r disk -n 0
monhmc -r proc -n 0
monhmc -r swap -n 0

  
shows total, used and free memory of HMC
shows filesystems and usage info
shows cpu usage of each processor
shows paging space usage


lshmc -V
lshmc -v
lshmc -n
  
HMC version
HMC model
lists the network settings of the HMC


lssvcevents -t console -d 60
lssvcevents -t hardware -d 30
lssvcevents -t console -d 7 | grep DLPAR
lssvcevents -t console -d 7 | grep Migration
  
lists console events in the past 60 days
list serviceable events which occured in the past 30 days
list DLPAR operations of last 7 days (you can grep more to mem or proc)
list last 7 days LPMs

HMC management commands


hmcshutdown -t 3 -r
hmcshutdown -t now
  
Reboot the HMC after 3 minutes
Halt the HMC immediately


lshmcusr
lshmcusr --filter "names=flecke"
lshmcusr --filter "names=flecke" --header -F name,taskrole,description,remote_webui_access
  
list users
list filtered user flecke
list parameter name,taskrole,description + remote_webui_access with header by filtered user flecke 

mkhmcusr -u flecke -a hmcsuperadmin -d "System Administrator"
   create new user with taskrole hmcsuperadmin and description "System Administrator"


chhmcusr -i "name=[USER],remote_webui_access=1"
chhmcusr -i "name=[USER],taskrole=hmcoperator"
chhmcusr -u [USER] -t passwd
  
change access to WEB GUI
change taskrole
change user password


HMC debugging

to create debug Information, you need to create a special user account

mkhmcusr -u hscpe -a hmcpe
pedbg -c -q 4
  
create user hscpe
collect debugging information for error analyzing


Managed System + LPAR commands

list connected systems

lssysconn -r all -F --header
lssysconn -r all -F "type_model_serial_num"
  
all values with header
defined field type_model_serial_num

list system resources

lssyscfg –r sys
lssyscfg -r sys -F name:type_model:serial_num
lssyscfg -r sys -m [Managed System] -F --header

  
all values
defined fields name, type_model + serial_num
all values with header for specified managed System

Summary of partitions on a managed system

lssyscfg -m [ManagedSystem] -r lpar
lssyscfg -m [ManagedSystem] -r lpar -F --header
lssyscfg -m [ManagedSystem] -r lpar --filter "lpar_names=[LparName]"
lssyscfg -m [ManagedSystem] -r lpar -F "name:lpar_id:lpar_type:state:default_profile"

  
all values
all values with header for specified managed System
all values with header for specified managed System and filtered LPAR name
defined fields name, lpar_id, lpar_type, state, default_profile

change configuration

chsyscfg -r sys -m [ManagedSystem] -i "new_name=pserver1"
chsyscfg -r lpar -m [ManagedSystem] -i "name=OldName,new_name=NewName"
chsyscfg -r prof -m [ManagedSystem] -i "name=default,lpar_name=Germany_Prod_1,boot_mode=norm"
chsyscfg -r prof -m [ManagedSystem] -i "name=[ProfileName],lpar_name=[LparName],uncap_weight=32"
  
rename managed system to name pserver1
rename LPAR from name OldName to NewName
change boot_mode from a defined LPAR Germany_Prod_1
changes weight in given profile

rmsyscfg -r lpar -m [ManagedSystem] -n [LparName]
   Remove LPAR

List installed I/O devices on HMC managed system

lshwres -r io --rsubtype unit -m [ManagedSystem]
lshwres -r io --rsubtype bus -m [ManagedSystem]
lshwres -r io --rsubtype slot -m  [ManagedSystem]
lshwres -r io --rsubtype slot -m [ManagedSystem] -Flpar_name,unit_phys_loc,bus_id,phys_loc,description, --header

  
by unit
by bus
by slot
by defined fields and slot

List processors, memory and hca’s on HMC managed system (system/lpar)

lshwres -r proc -m  [ManagedSystem] --level sys
lshwres -r proc -m  [ManagedSystem] --level lpar

  
by System
by LPAR

List memory on HMC managed system

lshwres -r mem -m  [ManagedSystem] --level sys
lshwres -r mem -m  [ManagedSystem] --level lpar

  
by System
by LPAR

List hca’s on HMC managed system

lshwres -r hca -m  [ManagedSystem] --level sys
lshwres -r hca -m  [ManagedSystem] --level lpar

  
by System
by LPAR

Lists all logical partitions and the MAC addresses of the virtual Ethernet
lshwres -r virtualio --rsubtype eth --level lpar -m [Model] -F lpar_name,mac_addr
  

changes resources of actual running config (it will not add to profile)

chhwres -r virtualio --rsubtype eth -m [ManagedSystem] -o s -p [LparName] -s [AdapterId] -a "addl_vlan_ids+=[VlanTag]"
chhwres -r virtualio --rsubtype eth -m [ManagedSystem] -o s -p [LparName] -s [AdapterId] -a "addl_vlan_ids-=[VlanTag]"
chhwres -r proc -m [ManagedSystem] -o a -p [LparName] --procunits 8
chhwres -r proc -m [ManagedSystem] -p  [LparName] -o s -a "uncap_weight=32"
  
adding VLAN TAG dynamically
removing VLAN TAG dynamically
additionally assign 8 processors
changes weight of actual running config

manage LPARs

chsysstate -r lpar -m [ManagedSystem] -o on -n [LparName] -f 
chsysstate -r lpar -m [ManagedSystem] -o on -n [LparName] -b sms
chsysstate -m [ManagedSystem] -r lpar -n [LparName] -o osshutdown
chsysstate -m [ManagedSystem] -r lpar -n [LparName] -o shutdown --immed
  
boot LPAR
boot LPAR into sms status
Shutdown an LPAR using the operating system
Shutdown an LPAR immediate

RMC connection


lspartition -dlpar
  
shows dlpar capable partitions
(it will show if RMC connection is OK between the HMC and LPAR)


lsrsrc IBM.MCP
or
lsrsrc IBM.ManagementServer #OLD command

resource 1:
        MNName            = "192.6.5.77"
        NodeID            = 5089136303073145144
        KeyToken          = "hmc2"
        IPAddresses       = {"192.6.5.55"}
        ConnectivityNames = {"192.6.5.77"}
        HMCName           = "7042CR4*06CDB1B"
        HMCIPAddr         = "192.6.5.55"
        HMCAddIPs         = "10.0.0.1"
        HMCAddIPv6s       = ""
        ActivePeerDomain  = ""
        NodeNameList      = {"aixccf13"}

 
display connected HMC from LPAR

Fix RMC connection

There are some basic commands that can be run to check status of RMC configurations and there are some dependancies on RSCT versions as to which commands you use. RSCT 3.1.x.x levels are the newest and included in AIX 6.1 TL6 or higher and RSCT 2.x.x.x are included in AIX 6.1 TL5 or lower. Following queries provide a quick method to assess RMC health.
On AIX 6.1 TL5 or lower, this fileset needs to be installed
lslpp -l csm.client

On AIX 6.1 TL6 or higher, his fileset needs to be 3.1.0.x level or higher
lslpp -l rsct.core.rmc

On all AIX versions, check if all IP and host IDs trusted.
/usr/sbin/rsct/bin/ctsvhbac

check if HMC are listed as a resource
For AIX 6.1 TL5 or lower
lsrsrc IBM.ManagementServer

For AIX 6.1 TL6 or higher
lsrsrc IBM.MCP

On HMC (as hscroot) check LPAR's DCaps value are non-zero
lspartition -dlpar

If you answer no to any of the above then corrective action is required.

Connections can be fixed with commands (run as root on LPAR, HMC, or both) below:
/usr/sbin/rsct/install/bin/recfgct
/usr/sbin/rsct/bin/rmcctrl -p

You would need a pesh password for your HMC if you need to run the above fix commands on the HMC.
You can try the following command first as hscroot:
lspartition -dlparreset

If that does not help you will need to request pesh passwords from IBM Support for your HMC so you can run the recfgct and rmcctrl commands listed above.

After running the above commands it will take several minutes before RMC connection is restored. The best way to monitor is by running the lspartition -dlpar command on the HMC every few minutes and watch for the target LPAR to show up with a non-zero DCaps value.

Connect to LPAR using vterm

mkvterm -m [ManagedSystem] -p [LparName]
mkvterm -m [ManagedSystem] --id [Number]
rmvterm -m [ManagedSystem]  -p [LparName]
rmvterm -m [ManagedSystem]  --id [Number]
~~.

  
open a vterm by LPAR Name
open a vterm by LPAR ID
close a vterm connection by LPAR Name
close a vterm connection by LPAR ID
logout from vterm session

...page...

usefull command syntax

list all servers configured on HMC in the form model_serial_number and configured lpars
for MODEL in `lssysconn -r all -F "type_model_serial_num"`
do
   lssyscfg -r lpar -m $MODEL -F"name,lpar_id,state"  | while read LPARS
   do
      echo "$LPARS,$MODEL"
   done
done


list configured processors on HMC defined managed systems
for MODEL in `lssysconn -r all -F "type_model_serial_num"`
do
   echo "Type-Model*SerialNumber=$MODEL"
   lshwres -r proc -m  $MODEL --level sys -F"configurable_sys_proc_units,curr_avail_sys_proc_units" --header
   lshwres -r proc -m  $MODEL --level lpar -F "lpar_name,lpar_id,curr_min_procs,curr_procs,curr_max_procs" --header
   echo
done


list configured memory on HMC defined managed systems
for MODEL in `lssysconn -r all -F "type_model_serial_num"`
do
   echo "Type-Model*SerialNumber=$MODEL"
   lshwres -r mem -m  $MODEL --level sys -F"installed_sys_mem,configurable_sys_mem,curr_avail_sys_mem" --header
   lshwres -r mem -m  $MODEL --level lpar -F "lpar_name,lpar_id,curr_min_mem,curr_mem,curr_max_mem" --header
   echo
done


list all configured IO defices on HMC defined managed systems
for MODEL in `lssysconn -r all -F "type_model_serial_num"`
do
   echo "Type-Model*SerialNumber=$MODEL"
   lshwres -r io --rsubtype slot -m  $MODEL -F "lpar_name,unit_phys_loc,bus_id,phys_loc,description" --header
   echo
done


full listing of configured processors, memory and IO devices on HMC defined managed systems
for MODEL in `lssysconn -r all -F "type_model_serial_num"`
do
   echo "Type-Model*SerialNumber=$MODEL"
   lshwres -r proc -m  $MODEL --level sys -F"configurable_sys_proc_units,curr_avail_sys_proc_units" --header
   lshwres -r proc -m  $MODEL --level lpar -F"lpar_name,lpar_id,curr_min_procs,curr_procs,curr_max_procs" --header
   lshwres -r mem -m  $MODEL --level sys -F"configurable_sys_mem,curr_avail_sys_mem" --header
   lshwres -r mem -m  $MODEL --level lpar -F"lpar_name,lpar_id,curr_min_mem,curr_mem,curr_max_mem" --header
   lshwres -r io --rsubtype slot -m  $MODEL -F "lpar_name,unit_phys_loc,bus_id,phys_loc,description" --header
   echo
done


min listing for processors and memory
for MODEL in `lssysconn -r all -F "type_model_serial_num"`
do
   echo "Type-Model*SerialNumber=$MODEL"
   lshwres -r proc -m  $MODEL --level sys -F"configurable_sys_proc_units" --header
   lshwres -r proc -m  $MODEL --level lpar -F"lpar_name,curr_procs" --header
   lshwres -r mem -m  $MODEL --level sys -F"configurable_sys_mem" --header
   lshwres -r mem -m  $MODEL --level lpar -F"lpar_name,curr_mem" --header
   echo
done


access the HMC from browser

https://HMC_Address/preloginmonitor/index.jsp(external link)

ASME -Accessing the Advanced System Management Interface using a Web browser

ASME access(external link)

HMC update methods

Method 1. Using SSH and the updhmc command.

If the HMC is configured for remote ssh access, the fix can be applied using the updhmc command.
  • Log in as hscroot
  • Apply the fix using the updhmc command.
    For further information on using the updhmc command run the command: man updhmc
    Example: Applying fix direct from the internet FTP site 
    updhmc -t s -h public.dhe.ibm.com -u anonymous -p abc123 -f /software/server/hmc/fixes/ MH01403 .iso -c -r

    Example: SCP fix to HMC and apply from local disk
    scp the fix to the hmc /tmp directory. 
    scp -scp MH01403.iso hscroot@:/tmp

    Apply fix from local file system. 
    updhmc -t l -f /tmp/MH01403.iso -c -r

    Example: Applying the fix from DVD
    Burn the fix to DVD-R (this can be as data or an iso image)
    Insert the media into the HMC and run the command: 
    updhmc -t m -r

    Example: Applying the fix from USB
    Copy the fix to USB flash drive.
    Insert the USB flash drive to the HMC. Wait several seconds.
    Locate the mount point using the command: 
    lsmediadev

    The output will be similar to the following: 
    device=/dev/cdrom,mount_point=/media/cdrom,type=1,description=CD/DVD
device=/dev/sdb1,mount_point=/media/sdb1,type=3,description=USB flash memory device

    Mount the drive using the command: 
    mount

    where is the USB mount point returned by lsmediadev (/media/sdb1 in the example above). Run the update command: 
    updhmc -t l -f  / MH01403.iso -r

    where is the USB mount point returned by lsmediadev

Method 2. Auto-install

  • Download the fix.
  • Burn the iso image to DVD-R.
    Ensure you select the CD burner software package's option to burn as an iso image file; do not burn the file as a "data file".
  • Verify the DVD was burned correctly
    If the DVD was burned correctly as an image, the root directory will contain one file named "cert2.pem" and one folder named "images".
  • Reboot the HMC with the DVD in the drive.
    • Locate the HMC system unit (there will be a tag with the model of 7310 or 7042)
    • Insert the DVD
    • Push and hold the power button until the HMC powers off.
    • Power back on by pushing and releasing the power button.
    • During the reboot (just after the "Starting HAL daemondone" step), the HMC will install the fix.
    • Remove the DVD from the drive
      The DVD must be removed from the drive before the next reboot to prevent it from re-installing. If the fix installs again, any changes made to user profiles since the upgrade may be lost.

Weblinks

Upgrading HMC

Upgrading the HMC from Version 7.3.x or Version 7.7.x to Version 7.7.8(external link)

POWER7 information

This information supports HMC machine types 7042-CR4, 7042-CR5, 7042-CR6, 7042-CR7, 7042-C06, 7042-C07, and 7042-C08.
Hardware Management Console operations(external link)
Hardware Management Console 7042-CR4, 7042-CR5, 7042-CR6, 7042-CR7, 7042-C06, 7042-C07, and 7042-C08 service(external link)

Download Sides:

Recovery ISO Images:
ftp://ftp.software.ibm.com/software/server/hmc/recovery_images/(external link)
Update ISO Images:
ftp://ftp.software.ibm.com/software/server/hmc/updates/ftp://ftp.software.ibm.com/software/server/hmc/updates/(external link)
for network installations:
ftp://ftp.software.ibm.com/software/server/hmc/network/(external link)

Fix Central

Fix Central provides fixes and updates for your system's software, hardware, and operating system.
http://www.ibm.com/support/fixcentral/(external link)


Das Originaldokument ist zu finden unter http://ccf-consulting.de/tiki-5.0/tiki-index.php?page=CCF_AIX_HMC