System Logs Overview Page

Navigation: Support > System Logs

Displays collected system information available on an Oracle FS System. You can view logs as well as create new logs from this page.

You can manage logs from this page, including sending logs to a Call-Home server, downloading logs to a user-defined location, deleting logs, and clearing logs.

File Name

Lists the name of the log file bundle containing the collected system information. (The logs are compressed in the tar format.)

Note: The log name includes two time stamps. In this example, A990033ZIO-130714104814-130718095816-PCP_EVT_FOUND_PILOT_CORE_FILE-e-02-02.tar, the two timestamps indicate:

The first field, 130714104814 is the time stamp of the previous log bundle created before the most recent log bundle was created. For example, if the last log file was created on July 14, 2013, at 10:48:14 am, that information is added to the first part of the log file bundle name.
The second field, 130718095816, is the time stamp of the log file that was created. For example, if a log file was created on July 18, 2013, at 9:58:16 am; the time and date is shown as 130718095816 in the log file name.

Time Collected

Identifies the time and date at which the download bundle was collected from the Oracle FS System.

Collection Type

Indicates the method by which the system logs are collected:

Manual: Indicates user initiated system logs.
Event Generated: Indicates event triggered system logs where the triggering event is also in the name of the log bundle. .
Periodic: Indicates periodic or schedule driven Call‑Home system or test logs. The periodic method is used to produce a small log that contains the entire system configuration and last 100 events.

Content

Identifies the types of system information that have been collected and are included in the current download bundle.

Size

Identifies the size of the download bundle.

Notes

Provides user-defined information about the system logs collection. This information is transferred in the header of the log bundle and may be used to identify the reason for this collection. For example, the user-defined information could include the Service Request number for tracking purposes.