HMC Command Reference

HMC Command Reference

HMC Version
Discription:Can get Version & Release details
lshmc -V

To Get HMC serial Num
Discription:Will get HMC serial Num and Product Info
lshmc -v

N/W conf of HMC
Discription: will Get HMC network Configurations
lshmc -n

To reboot HMC
Discription: Will reboot the HMC
hmcshutdown -t now -r Don't forgot -r option to reboot

List users
Discription:List the HMC user details
lshmcusr

Change HMC password
Discription: to change the HMC password (Please be careful with user name)
Syntax :chhmcusr -u -t passwd
Example : chhmcusr -u hscroot -t passwd Will change the hscroot password

To List All managed systems on HMC
Discription: List all Managed systems
lssysconn -r all

List LPARS by Managed system
Discription: List LPARS under a managed system (Physical Server)
Syntax : lssyscfg -m -r lpar -F name:state
Example :lssyscfg -m subha -r lpar -F name:state
Discription: will List all the Lpars under management server named subha

Check Status of LPARS
Discription:List all Lpar status in HMC
Power4 HMC : lslpars
Power 5 Above lssyscfg -r sys -F name:state Lists with lapr name and Status

What Is soft reset ??
Soft reset is just like shuting down the LPAR operating system or Applications & and bring it back. This Both conditions will use when system hangs and don't use hard reset first try with soft reset if we use hard reset without soft reset it may cause to crash lpar OS

Soft reset LPAR
Discription: Soft resets the LPAR if there is any problem
Power4 chsysstate -m -r lpar -n -o reset
Power 5 chsysstate -r lpar -m -o shutdown -n
Soft rests the p5 above LPAR's by HMC

Soft rest Full Partition
Discription: Soft resets the Manged system in Full Partition Mode
chsysstate -n -r sys -o reset


What is hard reset ??
Hard reset is Powering off the LPAR and bring it back.

Hard rest a LPAR
Description:Hard rest of a LPAR
Power 4 chsysstate -m -r lpar -n -o reset
Power 5 chsysstate -r lpar -m -o shutdown -n --immed

Hard rest Full Partition
Description:Hard reset the managed system in Full Partittion Mode
Power 4 chsystate -n -r sys -o off


Open server Console of a LPAR
Description:To get the Lpar Physical console
mkvterm -m -p

Close a Open Console of a LPAR
Description:To close the Opened console of a LPAR
rmkvterm -m -p

Open Conosle for full partition Mode
Description: To get managed sys console
power4 mkvterm -m

Note :Use two tidles (~~) and followed by .(dot) will Close the existing Terminal Opened by u.

Boot LPAR
Description:Boot p4 LPAR with specicfied profile name
Power4 chsysstate -r lpar -m -o on [-f
Power5 chsysstate -r lpar -m -o on -f -n

Change LPAR Name
Description:Change the lpar name from lpar1 to mylpar1
chsyscfg -r lpar -m -i "name=lpar1, new_name=mylapr1"

change the Managed sys Name
Description:Chnages the Managed sys name to power5
chsyscfg -r lpar -m -I "new_name=power5"

increase the Processing units
description:Increase additional 8 processing units to Lpar
chhwres -r proc -m -o a -p --procunits 8

HMC Logs : /var/hsc/log/hmclogger.log
cim server logs /var/hsc/log/cimserver.log

AIX Boot Process

AIX Boot process involves multiple levels. Each level has discussed below.

The first level is powering on the server... from here POST (Power On Self Test) will start.

POST

After you've turned on the power and the server is starting, the server's hardware is verified and checked for possible issues. This step is called power-on self-test (POST). While the server is running through its process, POST is checking the memory, keyboard, sound card, and network devices. During this time, if you wanted to enter stand-alone mode (single-user maintenance), you would click F5 or F6 after the keyboard has been initialized. However, in this article, no keystrokes are entered, and the server boots into its normal boot mode.

Bootstrap

After the POST process has finished, the bootstrap —or a smaller program used to load a larger program—is loaded into memory. The bootstrap then loads the Boot Logical Volume (BLV) into memory. After the BLV is loaded, the kernel takes over the boot process.

Boot Logical Volume and the bosboot command

The BLV is the location that contains AIX's bootable images. Typically, the BLV can be found on the local disk of the server. The BLV contains the AIX kernel, the rc.boot file, commands required during the boot process, and a trimmed-down version of the Object Data Manager (ODM).

To create bootable images, you use the bosboot command. Using bosboot, you create a boot file (that is, a bootable image) from a RAM disk, a file system, and a kernel. The bootable image is created along with interfaces with the server's boot Read-Only Storage (ROS) and Erasable Programmable Read-Only Memory (EPROM).

The AIX kernel

The AIX kernel stored in the BLV creates the / (root), /usr, and /var file systems in RAM. Keep in mind that these file systems as well as the kernel are stored in RAM initially during the operating system boot process. Because they are in RAM, they are not accessible to anything outside the BLV.

After the file systems have been loaded into RAM, the kernel executes the init process, which now takes over the boot process.

The init process

The AIX kernel loads the process init as process identifier (PID) 1. This process is the parent, or root, process to all other processes running on AIX. After the init process has been loaded and is running the boot process, init calls rc.boot.

The rc.boot file

The rc.boot file has three important cases of execution during the AIX boot-up process. The first section of rc.boot initializes the system's hardware to prepare it for the operating system to boot. A limited amount of devices needed to start the system are configured at this time with the Configuration Manager command cfgmgr.

During the second section of rc.boot, the file systems /, /usr, and /var as well as the paging space are mounted. After these file systems have been mounted, init is replaced with init on the disk as PID 1, and the RAM is cleared.

In the third and final section of rc.boot, the actual init process is executed from disk. When init is executed, the /etc/inittab file is read, and each item is executed. During this time, the /tmp file system is now being mounted to disk. Now that the system is in the last leg of the boot process, the cfgmgr command is run again on the remaining devices that were not configured in the first section of rc.boot.

HardWare Management Console Commands & overview

HMC Overview and Commands:
Hardware management Console Simply HMC. With help of HMC We can manage all our Logical Partitions and managed servers. This is Linced product that trademark of IBM.
Supported OS Platforms: IBM Unix (AIX) and Linux.
Features:
1. Manage all your logical and physical Servers under a comman point.
2.Powering off/On on servers.
3.Capacity on demand and virtuvalazation.
4.LPAR Creation and resource management (increase or decrease CPU/ Memory and N/W ).
5.Firmware installations and Upgrades (Firmware upgrade from HMC console is more faster
compare to normal server console).

HMC Interfaces:
HMC v7 Supports Web Based and Command line interfaces. Firefox will be nice one for fast and easy Browsing.
Note : HMC super admin is hscroot and default password is abc123.

HMC Types: we have two different types of HMC's currently avilable in Market
1.7042-C06 Desktop type HMC 2.7042-CR4 is Rack Mounted HMC.
7042-C06 has faster CPU's and twice the RAM as compared to 7042-CR4 (Large Enterprise).

HMC Max Considertations:
1.Maximum of 48 non 590/595 servers are Supported.
2.A Maximum of 32 590/595 Servers are supported.
3.For all systems the MX number of LPAR's is 254.
4.Max 2 HMC's can support one server at a time.

Some Of the Most Useful HMC Commands:
Consider here my HMC server name is subha and my managed system is reddy and My LPAR is rendla.

1.To cerify the version of your $lshmc -V (Will show Version Number and release Info).
Note:Power4 won't supports v3.x, v4.x supports Power5 & v7.x Supports Power6 and Higher.

aix Important files in AIX

/etc/defaultrouter:
Defines the systems default routers. Values must be separated with whitespace, # can be used for comments.

/etc/gateways:
Contains all the routes and default gateways for the system.

/etc/hostname.interface:
Contains the hostname of the system and should match the hostname defined in the /etc/hosts file. The file is named with the interface name, such as hostname.hme0 or hostname.le0

/etc/hosts:
Configures names and aliases of IP-addresses. Fields should be separated with Tab or white space.

/etc/inetd.conf:
Is the Internet services database ASCII file which contains a list of available network services.

/etc/inetd.conf:
Is the Internet server database ASCII file that contains a list of available servers. Is invoked by inetd when it gets an Internet request via a socket.

/etc/inetd.conf:
Is the Internet server database, used by the inetd daemon, which contains a list of available network services.

/etc/inittab:
Is a script used by init. Controls process dispatching.

/etc/inittab:
Controls process dispatching. Used by init.

/etc/inittab:
Is a script used by init. Controls process dispatching.

/etc/lilo.conf:
Is the configuration file used by the Linux Loader while booting.

/etc/modules.conf:
Loads modules specific options at startup.

/etc/mygate:
Defines the systems default router or gateway.

/etc/myname:
Specifies the real host name for the system.

/etc/netsvc.conf:
Specifies how different name resolution services will look up names.

/etc/nodename:
Specifies the real hostname for the system.

/etc/nologin:
Is a text file that, if it exists in /etc/, will prevent non-root users from logging in. If a user attempts to login, it will be shown the contents of the file, and then be disconnected.

/etc/nologin:
Is a text file message that is shown to the user who tries to log on during a system shutdown process. After the message appears the log on procedure ends.

/etc/nsswitch.conf:
Specifies how the lookup for different databases are performed and in what order. Lookups are done left to right.

/etc/nsswitch.conf:
Specifies how the lookup for different databases is done and in what order.

/etc/printcap:
Describes printers and allows dynamic addition and deletion of printers by the spooling system.

/etc/printcap:
Describes printers and allows dynamic addition and deletion of printers by the spooling system.

/etc/rc.conf:
Is a configuration file used to configure the system daemons. It has three sections, the first turns features on or off, the second turns daemons on or off and the third sets parameters for the
/etc/resolv.conf:
Configures the system's network. Specifies hostname and gateway.

/etc/xinetd.conf:
Contains the configuration for the extended internet services started by the xinetd command.