If you wish to be able to access an HMC from the command line, without the need of logging in, you can use ssh (secure shell).
Set-up a secure shell connection to your HMC:
# ssh userid@hostname
You will have to enter a password to get into your HMC.
To allow your root user direct access to the HMC without the need of logging in, you'll have to update the
authorized_keys2 file in the
.ssh subdirectory of the home directory of your HMC user. There's a problem: a
regular user only gets a restricted shell on an HMC and therefore is unable to edit the
authorized_keys2 file in subdirectory
.ssh. In an HMC version 3 it is possible to disable the restricted shell for users by editing file
/opt/hsc/data/ssh/hmcsshrc. In an HMC version 4 and up you no longer get root access (except, you may get it, by contacting IBM), so you can no longer edit this file.
But there's another way to accomplish it.
Let's say your hmc user ID is
hmcuser and you were able to logon to the HMC called
hmcsystem using this ID and a password (like described above).
First, get a valid
authorized_keys2 file, that allows root at your current host access to the HMC. Place this file in
/tmp.
Then, use
scp to copy the
authorized_keys2 file to the HMC:
# scp /tmp/authorized_keys2 hmcuser@hmcsystem:~hmcuser/.ssh/authorized_keys2
[Enter your hmcuser's password, when required]
Now, just test if it works:
# ssh hmcuser@hmcsystem date
You should now be able to access the system without entering a password.
As of Hardware Management Console (HMC) Release 3, Version 2.3, the rexec command is no longer available on the HMC. Use
ssh command instead. From Version 2.5, users are required to enter a valid HMC user id/password when downloading the WebSM client from the HMC. The URL for the WebSM client is: http://[HMC fully qualified domain name]/remote_client.html.
Standard users receive the restriced shell via a set -r in .mysshrc when logging in. Comment the set -r command in /opt/hsc/data/ssh/hmcsshrc to get rid of the restricted shell for your users (it gets copied to $HOME/.mysshrc). For more information on commands that can be used in restriced shell on the HMC, go to HMC Power 4 Hints & Tips.
A special hscpe user ID can be created which has unrestricted shell access via the pesh command. Use lshmc -v to determine the serial number of the HMC (after *SE). Then call IBM support and request for the password of the hscpe user for the pesh command. IBM is able to generate a password for the hscpe user for one day.
The uname -Ls command will show you the partition number and the partition (lpar) name. When setting the resource allocation for a partition profile, set the minimum to the absolute bare minimum, and set the maximum as high as possible.
For memory there are special considerations:
- If you set the maximum too low and you wish to exceed above the maximum amount of memory defined in the active profile, you can't simply adjust the profile and put extra memory in via DLPAR, because the LPAR has been initialized with a certain page table size, based on the maximum amount of memory setting. Therefore, a reboot will be required when you wish to use more memory than defined in the active profile. If you do try it however, you'll receive the following error:
HMCERRV3DLPAR018: There is no memory available for dynamic logical partioning on this partition.
- If you set the maximum too high, the partition will be initialize with a large page table size, which uses too much memory for overhead, which you might never use.
If you decide to update to HMC release 7.3.5, Fix Central only supplies you the ISO images.
This procedure describes how you can update your HMC using the network without having to sit physically in front of the console.
First, check if this new HMC level is supported by the firmware levels of your supported systems using this link. If you're certain you can upgrade to V7.3.5, then make sure to download all the required mandatory fixes from IBM Fix Central. Don't download the actual base level of HMC v7.3.5 of 3 Gigabytes. We'll download that directly to the HMC later on.
Then, perform the "Save upgrade data" task using either the Web interface or the command line. Then get the required files from the IBM server using ftp protocol using the following command:
# getupgfiles -h ftp.software.ibm.com -u anonymous --passwd ftp
-d /software/server/hmc/network/v7350
Hint: Once this procedure gets interrupted for any reason, you need to reboot your HMC before restarting it. Otherwise, some files will remain in the local download directory which will lead to incorrect checksums.
You can check the progress of the procedure using the command ls -l /hmcdump in a different terminal. Once it has finished, you will see a prompt without any additional messages and the directory will be empty (the files will be copied to a different location).
Then tell the HMC to boot from an alternate media by issuing the following command:
# chhmc -c altdiskboot -s enable --mode upgrade
Finally reboot your HMC with the following command from the console:
# hmcshutdown -r -t now
The installation should start automatically with the reboot. Once it has finished you should be able to login from remote again. The whole procedure takes up to one hour. Once you have finished you should add in any case the mandatory efixes for HMC 7.3.5 as ISO images. You can update the HMC with these fixes through the HMC. For more information, please visit
this page.
If your HMC is located behind a firewall and your only access is through SSH, then you have to use SSH tunneling to get browser-based access to your HMC. The ports you need to use for setting up the SSH tunnel are: 22, 23, 8443, 9960, 9735, 657, 443, 2300, 2301, 2302 and 12443. This applies to version 7 and up of the HMC. For example, if you're using a jump server to get access to the HMC, you need to run:
# ssh -l user -g -L 12443:10.48.32.99:12443 -L 8443:10.48.32.99:8443 -L 9960:10.48.32.99:9960 -L 9735:10.48.32.99:9735 -L 2300:10.48.32.99:2300 -L 2301:10.48.32.99:2301 -L 443:10.48.32.99:443 -L 2302:10.48.32.99:2302 -L 657:10.48.32.99:657 -L 22:10.48.32.99:22 -L 23:10.48.32.99:23 jumpserver.domain.com -N
When you've run the command above (and have logged in to your jumpserver), then point the browser to https://jumpserver.domain.com.
You can do something similar within PuTTY on your desktop system. Basically create a new PuTTY session to your HMC, and then in the SSH tunnel section, enter an entry for each port to the HMC, e.g. add port 12443 to 10.48.32.99:12443. Repeat this for all ports mentioned above and then save your PuTTY session. After that, login to your session, and open a browser to https://localhost, which should then redirect you to your HMC's web GUI.
Number of results found for topic
HMC: 15.
Displaying results: 11 - 15.
