1. Oracle ILOM User's Guide for System Monitoring and Diagnostics Firmware Release 5.1.x
  2. Viewing System Inventory, Health, and Performing Service and Management Actions
  3. Managing Oracle ILOM Log Entries
  4. Filter Log Entries

Filter Log Entries

Properties for filtering the server SP log entries are available in the CLI and web interface.

Note:

For a description of custom filters supported for each log type (Audit, Event, Session, or System), see the online help in the web interface. To access the help, click the More Details link at the top of the web page. For example, click System Log, then click the More Details link located at the top of the web page.

Note:

The Session log is only available in Oracle ILOM for KVMS or Serial Redirection connections opened on Oracle servers supporting Oracle ILOM 5.0.2 or later.
  1. To filter log entries for the server SP, perform one of the following steps:

    • From the web interface, select either a standard filter or a custom filter from the Filter list box.

      For further details about filtering log entries shown in the web interface, click the More Details link on the log page.

    • From the CLI, issue the show command followed by one or more supported log filter properties.

      For example:

      • To filter the audit, event, or session log entries using all the filter properties, type:

        show /SP/logs/ audit|event|session /list Class== class Type== type Severity== value

      • To filter the audit, event, or session log entries by Class, type:

        show /SP/logs/ audit|event|session /list Class== class

      • To filter the audit, event or session log entries by Class and Type, type:

        show /SP/logs/ audit |event|session /list Class== class Type== type

      • To filter the system log entries by Subcomponent or Event Type, type one of the following:

        show /System/Log/list Subsystem== subsystem

        show /System/Log/list Type== type

      Where:

      • subsystem is the subsystem component name, for example: System, Cooling, or Processor. For other examples, see the Subsystem examples listed in the Log Properties.

      • type is the event name or the component name where the event occurred, for example: OK, Warning, Service Required, Fann , Processorn , DCUn , DIMMn , UI, Product, Log, Update, or Action. For other examples, see the Component or Event Type examples listed in the Log Properties.

      • class is the class event name, for example: System, Fault, Chassis, Software, Audit, BIOS, or Sensor. For further information about the Class log property, see Class in the Log Properties.

      • severity is the event severity, for example: Debug, Down, Critical, Major, or Minor.

      • event|audit indicates a choice between the event and audit log. Type event to filter the event log, or type audit to filter the audit log.

Related Information