Rainsbrook

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Root access via pesh ======

From IBM support:-
 
1a.  Remote ssh and pesh method. \\
Log in as root using pesh procedure (see Rochester Support Center knowledgebase document 398762486, Accessing the\\ Product Engineering Shell (PESH) Command Line:   for further information).  Note:  This method requires that the\\ customer had remote command execution enabled and ssh (port 22) allowed in the firewall prior to the failure.  \\
\\ 
a  Log in to the HMC remotely using a ssh client such as putty with hscroot (or other hmcsuperadmin)\  \\
b  Create user hscpe  \\
mkhmcusr -u hscpe -a hmcpe \\
Note: If hscpe user exists but the password is lost, log in as hscroot and reset it using chhmcusr command.  For\\ example: chhmcusr -u hscpe -t passwd. Enter the new password for when prompted by "Enter the new password:."  \\
c  Log in remotely using ssh client (putty) using hscpe id created in 1b. \\
d  pesh <serial number>  \\
where <serial number>is the HMC serial number in upper case letters. \\
Note: The lshmc -v command cannot be used to obtain the serial number or date for the pesh password.  Get the serial\\ number from the label on the unit, the bios setup, or from the logs (grep "Hardware Management\\ Console" /var/adm/invscout/VPD/*.xml).  Date can be found using the date command. \\
e  Enter pesh password generated by support center representative (case sensitive). \\
f   su - \\
g  Enter root password. \\
Note: If the root password is lost (default is passw0rd), log in to another session as hscroot and reset it using\\ chhmcusr command.  For example: chhmcusr -u root -t passwd. Enter the new password for when prompted by "Enter the \\ new password:." \\
HMC should now be at a # prompt.  \\
 
2.  Remove hmclogger.log \\
After obtaining root access, do the following to clear the error: \\


o  Confirm cause of problem \\
ls -l /var/hsc/log/hmclogger.log \\
(the value returned is in bytes and should be over 10M) \\
 

o  Delete the log file \\
rm /var/hsc/log/hmclogger.log \\
 

o  Check for another 7.3.2 bug that causes performance issues. \\
ls -l /var/hsc/log/aca.log \\
If the owner is not ccfw (usually will show root), change the owner/group: \\
chown ccfw:ccfw /var/hsc/log/aca.log \\
 

o  Reboot\\