Do+Able Products 12347 User Manual Page 32

  • Download
  • Add to my manuals
  • Print
  • Page
    / 57
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 31
Hardware Management Console Best Practices
- 32 -
This password is valid until the end of the calendar day for which it was issued.
Hence, a password obtained at 11 pm will expire in one hour, i.e. midnight. Once
accepted, the password will give full shell access. Note that while the password
will expire at the end of the calendar day, once logged in as user root you may
remain logged in indefinitely. This is not recommended because it can be a
security exposure. It is recommended that this user ID be deleted after use and
recreated, temporarily, as needed.
6.2 Problem Logging and Tracking
More detailed information about either information or error messages received
during command execution can be obtained by using the showLog command.
This command can be run in an xterm on the HMC console by a user who has
become root. (In order to become root, you will need to follow the steps listed
above for obtaining a password to run in conjunction with the hscpe task role and
the pesh command.) This document in Information Center provides more details:
http://publib.boulder.ibm.com/infocenter/iseries/v1r2s/en_US/info/iphau/viewhm
clogs.htm#viewhmclogs
Any user except those with the hmcviewer task role can view system event
information included in the console logs on the GUI via the HMC Management ->
HMC Configuration -> View Console Events task. This will display system
events logged during HMC operation, enumerating HMC activity in response to
user-initiated tasks, whether the command succeeded or failed. This will not
display all entries in the HMC Console logs, but a subset of them. This task can
also be executed on the command line by using the ‘lssvcevents’ command
with ‘-t console’ flag.
6.3 Problem Correction
As mentioned previously, all HMC tasks - user-initiated and otherwise - require
interactions between various subsystems on the HMC. Failures in one or more
subsystems may occur, and it is very useful if failures can be isolated. For
example, usually when a task fails it’s a good idea to try another way to perform
the same operation. Assume a task cannot be performed from the GUI; it was
initiated and the GUI “hung.” Typically, this means the panels are grayed out,
especially after minimizing and maximizing. Check whether it can be done
through the command line. If that can be performed successfully, most likely the
GUI is the problem. If both ways do work, then the backend is likely to be the
culprit.
With that being said, let’s consider some possible scenarios in HMC system
management. A common source of curiosity is HMC performance. On the HMC
Page view 31
1 2 ... 27 28 29 30 31 32 33 34 35 36 37 ... 56 57

Comments to this Manuals

No comments