The All Problems pane displays all
the problems (service requests) for systems that are monitored by IBM® Electronic Service Agent.
Before you begin
The System reference codes (SRCs) indicate a storage complex hardware or
software problem that can originate in hardware or in Licensed Internal Code. A storage complex
component generates an error code when it detects a problem. An SRC identifies the component that
detected the error code and describes the error condition. The table shows the possible SRC codes -
Table 1. System reference codes
System Reference Code |
Description |
5xxxxxxx |
Reference codes |
A1xxxxxx |
Service processor reference (attention) codes |
AAxxxxxx |
Partition firmware reference (attention) codes |
B1xxxxxx |
Service processor firmware reference codes |
B7xxxxxx |
Licensed Internal Code reference codes |
BAxxxxxx |
Partition firmware reference (attention) codes |
DAxxxxxx |
Partition firmware reference (error) codes |
For a detailed list of SRC codes, see System Reference
Codes.
About this task
You can use the IBM
Electronic Service Agent graphical user
interface to view problems, delete problems, and update the service request status. Electronic Service Agent does not collect any error data
or problem information for Admin_notify type of events and duplicate events. The problem information
and error data are collected for the problems that are meant to be transmitted to IBM support.Tip: You can also use the
esacli
problem command to view problems. For information, see
esacli problem.
To
filter or search for a particular problem that you require, go through the following steps:
- Click the Define filter
icon. The
Filter window is displayed.
- Specify the rules to filter the problems and click Filter. A list of
filtered problems is displayed
To view problems, follow these steps:
Procedure
- Access and log in to the IBM Electronic Service
Agent graphical user interface.
- Click Main menu from
left navigation.
- Click All Problems tab.
The
Problems table displays the following information:
- Name - Displays the name of the system that has problems. If you are
viewing All Problems, then you can filter the problems for a particular
system.
- Severity - Displays the severity of the problem.
- Description - Provides a short description of the problem
identified.
- SRC - Displays the alphanumeric system reference code (SRC) that is
assigned to the problem by the system.
- Time of Occurence - Displays the time stamp of the problem
occurrence.
- Service request - Displays the system request identifier (PMR number)
that is assigned to the problem by the system.
- Service request status - Displays the service request status (PMR status)
that is associated with problem. For example, Open,
Processing, or Closed.
- Local Problem Status - Displays the reporting status
of the problem. The status can be one of the following -
- Detected - ESA identified the problem.
- Open - No action is taken on the problem.
- Pending - The problem is being sent to IBM support.
- Failed - All attempts to send the problem information to IBM support is
failed. No more attempts can be made.
- Reported - The problem is sent to IBM support.
- Closed - The problem is processed and closed.
- Expired - The IEPD problem is purged.
- Email sent - ESA sends an email notification about the problem to the
registered administrator.
- Failed to send email - ESA fails to send an email notification about the
problem.
- Duplicate - For any existing problem (same problem for same system) that
notifies through email and also that has the Local Problem Status as
Email sent, the problem is reported as duplicate.
- Cancelled - The problem is canceled. A problem will be marked
Duplicate until an Email sent problem is canceled.
- Local Problem ID - Displays the status of the problem, for example,
Opened, Closed, Detected,
Failed, Reported, or Expiredstate.
- Duplicate Of - Displays the ID of the problem that it is a duplicate
of.
- Select a problem in the list to take one of
the following actions:
You can also send a test problem to see whether the problem
is reporting correctly. For more information, see Sending a test problem.