IBM Power System POWER7 Series, Общие процедуры обслуживания

Страница: 73 / 198

3. Log on to ASMI by using the administrator user ID and password.
Displaying error and event logs
You can view error and event logs that are generated by various service processor firmware components.
The content of these logs can be useful in solving hardware or server firmware problems.
To perform the display operation, your authority level must be one of the following values:
v
General
v Administrator
v
Authorized service provider
Informational and error logs can be viewed by all authority levels. Hidden error logs can be viewed by
authorized service providers.
The following table shows error log types that might be displayed, the conditions that make an error log
specific to that error log type, and the user authority level that you need to view specific types of error
logs.
Error log type
Conditions
User availability Severity Action
Informational logs Informational Report to operating
system (OS) but not
hidden Available to all users
Error logs Not informational Report to OS but not
hidden Available to all users
Hidden logs Not informational and
informational Report to OS, hidden, or
both Available only to the
authorized service
provider and users with
higher authority.
To view error and event logs in summary or full detailed format, do the following steps:
1. On the ASMI Welcome pane, specify your user ID and password, and click Log In .
2. In the navigation area, expand System Service Aids and click Error/Event Logs . If log entries exist, a
list of error and event log entries is displayed in a summary view.
3.
To view the full detail format of any of the logs listed, select the log's corresponding check box and
click
Show details . When multiple logs are selected, any action applies to each selected log. The full
detail information might span several pages. The contents and layout of the full detail output is
defined by the event or error logging component.
4. Click Mark as reported to mark platform error entries whose underlying causes have been resolved.
By doing so, these entries are not reported to the operating system again when the system reboots.
After they are marked, these errors can be overwritten by other errors logged in the service processor
history log.
Note: The Mark as reported button is available only when your authority level is an authorized
service provider.
Setting the system enclosure type
Use this procedure to set values that uniquely identify the type of enclosures attached to the system.
When setting the system enclosure type, ensure that the Enclosure serial number field matches the
original value, which can be found on a label affixed to the unit. Updating the Enclosure serial number
field keeps the configuration and error information synchronized, and this information is used by the
Common service procedures
59