| -t EventType |
The type of event to list: - console
- Console events - events created by the applications
- Attributes: time, userid, pid, name, category, severity,
time_bin, text
- Filters: severities, categories, name
|
| |
- hardware
- Serviceable events
- Attributes: problem_num, pmh_num, refcode, status, first_time,
last_time, sys_name, reporting_name, sys_mtms, reporting_mtms, enclosure_mtms,
failing_mtms, text, firmware_fix, created_time, analyzing_sfp, refcode_extension,
firmware_pkg_name, firmware_pkg_status, reporting_sfp_name, reporting_sfp_mtms,
failing_sfp_mtms, severity, lpar_id, lpar_name, lpar_hostname, lpar_os_type,
notification_type, notification_status, duplicate_count, analyzing_sfp_mtms,
analyzing_sfp_name, called_home_sys_mtms, sys_log_id, platform_log_id,
subsystem_id, creator_id, ipl_state, symptom, failing_lpar_id, failing_lpar_name,
failing_lpar_os_type, fru_part_nums, fru_phys_locs, first_time_bin,
last_time_bin, created_time_bin
- Filters: status, problem_nums, refcodes, fru_part_nums,
fru_phys_locs, reporting_mtms, failing_mtm
|
| |
- fru
- Field replaceable units (frus) for a serviceable event.
- Attributes: part_num, class, description, phys_loc, prev_replaced,
replaced_time, serial_num, replacement_grp, ccin, logic_ctl_mtms,
power_ctl_mtms, replaced_time_bin
- Filters: problem_nums (required)
|
| |
- comment
- Comments for a serviceable event.
- Attributes: time,commenter,text
- Filters: problem_nums (required), status
|
| |
- service_object
- Service objects for a serviceable event. These are not accessible
to users without the DEUser or SRUser roles.
- Attributes: key, sys_log_id, notification_type, platform_log_id,
severity, creator_id, refcode, subsystem_id, lpar_os_type, failing_mtms,
text, lpar_id, lpar_name, lpar_hostname, first_time, last_time, duplicate_count,
eed_ptr, first_time_bin, last_time_bin
- Filters: problem_nums (required), status
|
| |
- dlpar
- Status of dynamic LPAR events - events used to synchronize resources
that can be dynamically configured while the partition is active.
These can be used to determine why the runtime and pending values
of a resource are not synchronized. Typically, the last two status
records are stored per partition per resource type.
- Attributes: lpar_id, resource_type, sequence_num, status_code,
time, internal_rc, drmgr_cmd, drmgr_rc, drmgr_stdout, drmgr_stderr
- Filters: lpar_ids, resource_types
|
| -d NumberDays |
The number of previous days for which to view
events. This might not be used with the -i flag, and is only
applicable to -t console, and -t hardware.
If this flag and the -i flag are omitted, the default is 7
days. |
| -i NumberMinutes |
The number of minutes for which to view events.
This might not be used with the -d flag, and is only applicable
to -t console, and -t hardware. |
| -m ManagedSystem |
The name of the managed system. This attribute
is optional because there is only one system to manage. The name might
either be the user-defined name for the managed system, or be in the
form tttt-mmm*ssssssss, where tttt is the machine type, mmm is the
model, and ssssssss is the serial number of the managed system. |
| --filter FilterData |
The filters to apply to the resources to be
listed. Filters are used to select which resources of the specified
resource type are to be listed. If no filters are used, then all of
the resources of the specified resource type will be listed. For example,
specific partitions can be listed by using a filter to specify the
names or IDs of the partitions to list. Otherwise, if no filter is
used, then all the partitions in the managed system will be listed. The
filter data consists of filter name/value pairs, which are in comma
separated value (CSV) format. The filter data must be enclosed in
double quotation marks.
The format of the filter data is as
follows: "filter-name=value,filter-name=value,..."
Note
that certain filters accept a comma separated list of values, as follows: ""filter-name=value,value,...",..."
When
a list of values is specified, the filter name/value pair must be
enclosed in double quotation marks. Depending on the shell being used,
nested double quotation marks might need to be preceded by an escape
character, which is usually a '\' character.
Unless otherwise
indicated, multiple values can be specified for each filter.
Valid
filter names for -t console:
severities, categories, name
Valid
filter names for -t hardware:
status, problem_nums, refcodes,
fru_part_nums, fru_phys_locs, reporting_mtms, failing_mtms
Valid
filter names for -t fru:
problem_nums (required)
Valid
filter names for -t comments and -t service_objects:
problem_nums
(required), status
Valid filter names for -t dlpar:
lpar_ids,
resource_types
|
| -F AttributeNames |
A delimiter separated list of attribute names
for the desired attribute values to be displayed for each resource.
If no attribute names are specified, then values for all of the attributes
for the resource will be displayed. When this option is specified,
only attribute values will be displayed. No attribute names will be
displayed. The attribute values displayed will be separated by the
delimiter which was specified with this option.
This option
is useful when only attribute values are desired to be displayed,
or when the values of only selected attributes are desired to be displayed.
Attribute
names:
|
| |
- analyzing_sfp
- Name or MTMS of the service focal point system analyzing the
event.
|
| |
- analyzing_sfp_mtms
- MTMS of the service focal point system analyzing the event.
|
| |
- analyzing_sfp_name
- Name of the service focal point system analyzing the event.
|
| |
- called_home_sys_mtms
- MTMS of the system to which the event was called home.
|
| |
- category
- Category or client type of the console event. Valid values:
- GUI: Web interface
- CLI: Command line interface
- AP: Access process
|
| |
- ccin
- CCIN of the FRU
|
| |
- class
- Class or type of the FRU
|
| |
- commenter
- Name of the person adding a comment to the event
|
| |
- created_time
- Time the event was created.
|
| |
- creator_id
- The ID of the entity that created the event. Valid values:
- C: Hardware Management Console
- E: Service processor
- H: POWER Hypervisor™
- W: Power
- L: Partition firmware
- S: Licensed Internal Code
for IBM® i
|
| |
- description
- Description of the FRU
|
| |
- drmgr_cmd
- The command used for a dynamic LPAR event. The drmgr command
is run on the client partition's operating system to synchronize a
particular resource.
|
| |
- drmgr_rc
- The return code for the command used for a dynamic LPAR event.
The drmgr command is run on the client partition's operating system
to synchronize a particular resource.
|
| |
- drmgr_stdout
- The standard output for the command used for a dynamic LPAR event.
The drmgr command is run on the client partition's operating system
to synchronize a particular resource.
|
| |
- drmgr_stderr
- The standard error for the command used for a dynamic LPAR event.
The drmgr command is run on the client partition's operating system
to synchronize a particular resource.
|
| |
- duplicate_count
- Number of duplicates for this event.
|
| |
- enclosure_mtms
- Enclosure MTMS
|
| |
- failing_lpar_id
- Unique ID for the failing partition
|
| |
- failing_lpar_name
- Name of the failing partition
|
| |
- failing_lpar_os_type
- Operating system type of the failing partition
|
| |
- failing_mtms
- MTMS of the failing system
|
| |
- failing_sfp_mtms
- MTMS of the failing systems service focal point
|
| |
- firmware_fix
- Indicates whether a firmware fix is available for the event
|
| |
- firmware_pkg_name
- Package name of a possible firmware fix
|
| |
- firmware_pkg_status
- Package status of a possible firmware fix
|
| |
- first_time
- First time this event was reported
|
| |
- fru_part_nums
- Part numbers of the FRUs
|
| |
- fru_phys_locs
- Unique physical location codes of the FRUs
|
| |
- internal_rc
- The return code for a dynamic LPAR event. This will be non zero
only if the dynamic LPAR command was unexpectedly not able to be sent
to the client partition.
|
| |
- ipl_state
- State of the system when this event occurred
|
| |
- key
- Unique ID for a service object for a particular serviceable event.
|
| |
- last_time
- Last time this event was reported
|
| |
- logic_ctl_mtms
- MTMS of the unit that logically controls the unit that the FRU
is located in
|
| |
- lpar_hostname
- Hostname of the partition that created this event
|
| |
- lpar_id
- ID of the partition that created this event
|
| |
- lpar_name
- Name of the partition that created this event
|
| |
- lpar_os_type
- Operating system type of the partition that created this event
|
| |
- name
- Name of the application that created the console event
|
| |
- notification_status
- The status of the notification type
|
| |
- notification_type
- The notification type for the event. Valid values:
- Yes: Call home
- No: Customer notify
|
| |
- part_num
- Part number of the FRU
|
| |
- phys_loc
- Unique physical location code of the FRU
|
| |
- pid
- Process ID of the process generating the console event
|
| |
- platform_log_id
- Unique ID of the platform log for this event
|
| |
- pmh_num
- PMH or tracking number
|
| |
- power_ctl_mtms
- MTMS of the unit that power controls the unit that the FRU is
located in
|
| |
- prev_replaced
- Indicates if the FRU has been previously replaced
|
| |
- problem_num
- A unique ID for the event
|
| |
- refcode
- Reference code for the event
|
| |
- refcode_extension
- Extended reference code for the event
|
| |
- replaced_time
- Time the FRU was replaced
|
| |
- replacement_grp
- Replacement priority and grouping for the FRU. Valid values:
- H: Multiple high priority FRUs should be acted on as a group
- M: Medium priority FRUs should be acted on, one at a time, in
the order given.
- A: Medium priority group A FRUs should be acted on as a group.
- B: Medium priority group B FRUs should be acted on as a group.
- C: Medium priority group C FRUs should be acted on as a group.
- L: Low priority FRUs should be acted on only after all other priority
call-outs failed to resolve the problem.
|
| |
- reporting_mtms
- MTMS of the reporting unit
|
| |
- reporting_name
- Name of the reporting unit
|
| |
- reporting_sfp_mtms
- MTMS of the service focal point reporting the event
|
| |
- reporting_sfp_name
- Name of the service focal point reporting the event
|
| |
- resource_type
- The resource type for the dynamic LPAR event. These are all the
resources that can be dynamically reconfigured. Valid values:
- mem
- proc
- proc_units
- uncap_weight
- memory
- io_entitled_mem
- mem_weight
|
| |
- sequence_num
- The sequence number for this dynamic LPAR event. Each resource
type might have more than one entry. The sequence number distinguishes
the entries, and increments over time.
|
| |
- serial_num
- Serial number of the FRU
|
| |
- severity
- Severity of the event. Valid values:
- 10: Recovered error, general (10)
- 20: Predictive error, general (20)
- 21: Predictive error, degraded performance (21)
- 22: Predictive fault might be corrected after platform re-IPL
(22)
- 23: Predictive error, fault might be corrected after IPL, degraded
performance (23)
- 24: Predictive error, loss of redundancy (24)
- 40: Unrecovered error, general (40)
- 41: Unrecovered error, bypassed with degraded performance (41).
- 44: Unrecovered error, bypassed with loss of redundancy (44)
- 45: Unrecovered error, bypassed with loss of redundancy and performance
(45)
- 48: Unrecovered error, bypassed with loss of function (48)
- 60: Error on diagnostic test, general (60)
- 61: Error on diagnostic test, resource might produce incorrect
result (61)
|
| |
- status
- Status of the event. Valid values:
- Open: Event is in the open state
- Closed: Event has been closed
|
| |
- status_code
- Status code for the event. Valid values for dynamic LPAR events:
- 0: Synchronization successful
- 1: Synchronization in progress
- 2: Resource will not synchronize because the partition is a workload
group participant
- 3: Resource will not synchronize because the partition communication
state is not active
- 4: Resource will not synchronize because the partition does not
support dynamic LPAR of this resource type
- 5: Resource will not synchronize because the partition is not
in the Running state
- 6: Resource will not synchronize because the partition is unable
to remove any more memory dynamically
- 7: Resource will not synchronize because the synchronization command
failed to run for an unknown reason
- 8: Resource is not synchronized because the RMC command failed.
The system will retry. If the partition is in the Running state with
an active network connection, check the return code and contact your
support representative.
- 9: Resource is not synchronized because the drmgr command on the
partition failed. The system will retry. Check the return code, and
the command output.
- 10: Resource will not synchronize because the requested assigned
value is less than the current minimum. Restart your partition in
order to complete the synchronization.
- 11: Resource will not synchronize because the requested assigned
value is greater than the current maximum. Restart your partition
in order to complete the synchronization.
- 12: Resource will not synchronize because the pending and current
processing modes do not match. Restart your partition in order to
complete the synchronization.
- 13: Resource will not synchronize because IVM is unable to determine
dynamic LPAR capabilities of the logical partition.
- 255: Resource synchronization has not yet been attempted. It might
take a few seconds depending on your system utilization before synchronization
is attempted.
|
| |
- subsystem_id
- The subsystem causing the event. Valid values include:
- 10 - 1F: Processor subsystem including internal cache
- 20 - 2F: Memory subsystem including external cache
- 30 - 3F: I/O subsystem (hub, bridge, bus)
- 40 - 4F: I/O adapter, device and peripheral
- 50 - 5F: CEC hardware
- 60 - 6F: Power/Cooling subsystem
- 70 - 79: Other subsystem
- 7A - 7F: Surveillance error
- 80 - 8F: Platform firmware
- 90 - 9F: Software
- A0 - AF: External environment
|
| |
- symptom
- Symptom of the event
|
| |
- sys_log_id
- Unique ID of the system log for the event
|
| |
- sys_mtms
- MTMS of the system
|
| |
- text
- Text of the event
|
| |
- time
- Time of the console or dynamic LPAR event
|
| |
- time_bin
- Time in milliseconds since Jan 1, 1970
|
| |
- userid
- User ID of the user that ran the command that caused the console
event
|
| --header |
Display a header record, which is a delimiter
separated list of attribute names for the attribute values that will
be displayed. This header record will be the first record displayed.
This option is only valid when used with the -F option. |
