LPAR facts
To list all the Lpar in the managed system
- For initially configuring a P-Series system for installtion in LPAR mode, the system should be placed on Partion Stand-By mode
To list all the PCI slots allocated to an LPAR
# lsslot -c pci # lsslot -c pci -a
To dynamically reallocate an adapter
- Determine the PCI slot for the adapter using lsslot -c slot and get the "pciX' device name
- Remove the device from AIX using rmdev -l pciX -R (-R to remove all the child to parent)
- On HMC dynamically allocate the device to another
- On the destination box, run 'cfgmgr' to configure the allocated device
The HMC itself can be rebooted by loging to HMC with SSH, as user hscroot, and issueing the command
$ hmcshutdown -r -t0
To shutdown a LPAR
chsysstate -r lpar -m MACHINE_NAME -o shutdown --immed --restart --id LPARID (or -n LPARNAME)
To findout which HMC an LPAR is connected
# lsrsrc IBM.ManagementServer (Name and Hostname are HMC's Name and hostname of HMC)
Resource Persistent Attributes for IBM.ManagementServer
resource 1:
Name = "10.253.1.22"
Hostname = "10.253.1.22"
ManagerType = "HMC"
LocalHostname = "10.253.1.54"
ClusterTM = "9078-160"
ClusterSNum = ""
ActivePeerDomain = ""
NodeNameList = {"err3qdb0"}
resource 2:
Name = "128.137.44.205"
Hostname = "128.137.44.205"
ManagerType = "HMC"
LocalHostname = "10.253.1.54"
ClusterTM = "9078-160"
ClusterSNum = ""
ActivePeerDomain = ""
NodeNameList = {"err3qdb0"}
To disable/enable processor simultaneous multi-threading mode
smtctl -m off
If dynamic LPAR is not working
- Start rsct daemons if not already started
- lssrc -a | grep rsct
- startsrc -g rsct
- Try re-booting HMC
Console Using HMC Command Line
vtmenu
vtmenu is a Perl script which displays a list of partitions, opening a virtual terminal on the one selected. If more than one managed systems exists, a list of them is displayed first. After a managed system is selected, a list of all logical partitions on that managed system is displayed. The vtmenu command does not accept any flags or parameters and ignores all that are specified.
vtmenu is a Perl script which displays a list of partitions, opening a virtual terminal on the one selected. If more than one managed systems exists, a list of them is displayed first. After a managed system is selected, a list of all logical partitions on that managed system is displayed. The vtmenu command does not accept any flags or parameters and ignores all that are specified.
Escape sequence to leave vtmenu terminal session is:
~.
mkvterm: mkvterm opens a virtual terminal session for an AIX, Linux, or virtual I/O server partition
To open a console terminal:
$ mkvterm -m-p
This can be exited with ~~.
To remove a terminal someone else is using:
$ rmvterm -m-p
# lsslot -c phb
PHB Name Description Device(s)
PHB 1 Logical PCI Host Bridge pci0
U7879.001.DQDGTGK-P1-T14 pci3 sisscsia0
U7879.001.DQDGTGK-P1-T4 pci4 usbhc0 usbhc1
U7879.001.DQDGTGK-P1-T6 pci5 ent0 ent1
PHB 2 Logical PCI Host Bridge pci1
U7879.001.DQDGTGK-P1-C3 pci6 ent2 ent3
U7879.001.DQDGTGK-P1-C4 pci7 ent4 ent5
U7879.001.DQDGTGK-P1-C5 pci8 fcs0
PHB 3 Logical PCI Host Bridge pci2
U7879.001.DQDGTGK-P1-T12 pci10 sisscsia1
U7879.001.DQDGTGK-P1-T15 pci11 ide0
U7879.001.DQDGTGK-P1-C1 pci12 fcs1
To list the system connections
# lssysconff -r all
- lssysconn lists connection information for all of the systems and frames managed by this Hardware Management Console (HMC). Connection information for all systems and frames to which this HMC is connected or attempting to connect is listed.
- ssysconn also lists IP addresses that cannot be automatically discovered by this HMC when using DHCP. If this HMC is set up as a DHCP server on a private network, whenever the Remove Connection task or the rmsysconn command is run to remove a managed system or a managed frame from the HMC, the HMC places the IP address(es) of that system or frame in a list of removed IP addresses. Any IP address in that list will not be rediscovered when reattached to the HMC. The lssysconn -r nondiscover command can be used to display the contents of that list of removed IP addresses.
To list All the managed systems attached to the HMC
$ lssyscfg -r sys name=Server-9119-595-SN02898EB,type_model=9119-595,serial_num=02898EB,ipaddr=10.128.253 ndary=10.128.255.252,state=Operating,sys_time=10/13/2006 20:15:55,power_off_policy=1,co cod_proc_capable=1,hca_capable=1,huge_page_mem_capable=unavailable,micro_lpar_capable=1 ,5250_application_capable=0,redundant_err_path_reporting_capable=1,shared_eth_failover g_passing_capable=1,sp_failover_capable=1,vet_activation_capable=1,virtual_io_server_c 250_cpw_percent=0,max_lpars=254,max_power_ctrl_lpars=1,service_lpar_id=3,service_lpar_n ............................... ............................... ,pend_mfg_default_boot_mode=norm,sp_failover_enabled=1,sp_failover_state=Ready
To list only name, Serial number, IP address and state alone,
$ lssyscfg -r sys -F name,type_model,serial_num, ipaddr,state --header name,type_model,serial_num,ipaddr,state Server-9119-595-SN02898EB,9119-595,02898EB,10.128.253.255,Operating Server-9119-595-SN02898BB,9119-595,02898BB,10.128.255.250,Operating
$ lssyscfg -r lpar -m Server-9119-595-SN02898EB lssyscfg -r lpar -m Server-9119-595-SN02898EB name=eraprci0,lpar_id=8,lpar_env=aixlinux,state=Running,resource_config=1,os_version=0. 0.0.0.0.0,logical_serial_num=02898EB8,default_profile=eraprci0,curr_profile=eraprci0, work_group_id=none,shared_proc_pool_util_auth=0,power_ctrl_lpar_ids=none,boot_mode=norm, lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0 name=eraptci0,lpar_id=7,lpar_env=aixlinux,state=Running,resource_config=1,os_version=0. 0.0.0.0.0,logical_serial_num=02898EB7,default_profile=eraptci0,curr_profile=eraptci0, work_group_id=none,shared_proc_pool_util_auth=0,power_ctrl_lpar_ids=none,boot_mode=norm, lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0 name=erep2ci0,lpar_id=6,lpar_env=aixlinux,state=Running,resource_config=1,os_version=0. 0.0.0.0.0,logical_serial_num=02898EB6,default_profile=erep2ci0,curr_profile=erep2ci0, work_group_id=none,shared_proc_pool_util_auth=0,power_ctrl_lpar_ids=none,boot_mode=norm, lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0
$ lssyscfg -r lpar -m Server-9119-595-SN02898EB -Fname,curr_profile,state eraprci0,eraprci0,Running eraptci0,eraptci0,Running erep2ci0,erep2ci0,Running lshwres -r mem --level sys configurable_sys_mem=32768,curr_avail_sys_mem=30208,pend_avail_sys_mem=30208,installed_sys_mem=32768,deconfig_sys_mem=0,sys_firmware_mem=512, mem_region_size=128,pend_mem_region_size=128,"possible_mem_region_sizes=auto,16,32,64,128,256",auto_mem_region_size=128,max_mem_pools=0, max_paging_vios_per_mem_pool=1
Upgrading the machine code on HMC
01. Backup the managed system's profile data
Server and Partition --> Server Management --> Profile data --> Backup Type the filename and save the information. Do this for each Managed system.
02. Backup critical console information so that previous levels can be restored in the event of a problem while upgrading the software. Do not use this critical console data after a successful upgrade to a new version of the HMC software. We can backup the console data in DVD-RAM media
03. Record the current HMC configuration
04. Save upgrade data. You can save the current HMC configuration in a designated disk partition on the HMC. Only save upgrade data immediately prior to upgrading your HMC software to a new release. This action allows you to restore HMC configuration settings after upgrading
HMC Code update --> Save Upgrade Data --> Save on Hard Drive --> Finish
05. Upgrade HMC Software
HMC Management --> Shutdown or Restart HMC --> Restart HMCAfter HMC restarts, in the login screen, select
upgrade --> upgrade from Media -- Finish
No comments:
Post a Comment