Event Information Tools: IPMI Event Viewer Command Line Interface

ManualsBrandsHP ManualsSoftwareHP-UX Online Diagnostics Software

Table of Contents

User Interface

Directories

Report formats

Error Handling

Messages

Functional Specifications

Performance

Valid Configurations

Standards/Guidelines/Policies/Conventions

IPMI Event Viewer Command Line Interface

***This is the user guide for the CLI only***

User Interface

Overall Interface Description

The command line interface options are designed to be as similar as possible to the options for event log viewing on

the MP.

Syntax and Semantics of UI

Syntax for the command "slview".

Usage:

slview -d [-k|-r|-t|-v [logentry] [-a level|-c cell] [-p platform] -f <file>

slview -v logentry [-p platform] -f <file>

slview [-k|-r|-t|-v] [-a level|-c cell] [-p platform] -f <file>

slview [-k|-r|-t|-v] -x <hexevent> [-p platform]

Options:

-d

Dumps report of the entire log file without pausing and

sends to standard out. By default, the report is paged.

Summary of content (7 pages)

PAGE 1
Table of Contents User Interface Directories Report formats Error Handling Messages Functional Specifications Performance Valid Configurations Standards/Guidelines/Policies/Conventions IPMI Event Viewer Command Line Interface ***This is the user guide for the CLI only*** User Interface Overall Interface Description The command line interface options are designed to be as similar as possible to the options for event log viewing on the MP. Syntax and Semantics of UI Syntax for the command "slview".
PAGE 2
-x Decodes a specific event by specifying the value as 2 64-bit numbers. -k|-r|-t|-v [] Reports format by keyword (k) (default), raw hex (r), text (t), or verbose problem/cause/action data (v). You can go between formats in an interactive session. The choices are mutually exclusive on the command line. The verbose option (v) also allows specification of a single log entry with the -d option. Event numbers are shown in the keyword, text, and verbose log file formats.
PAGE 3
SMS releases: Windows An event file name on the SMS, commonly stored in the Windows directory C:\Program Files\Hewlett-Packard\EIT\var\log. MUST be specified unless the -x option is used. HP-UX For HP-UX SMS based systems, the event files are stored in the directory /var/smstools/log. HWE (Hardware Enablement) releases: An event file name on the server, commonly stored in the /var/stm/log/os directory with the file name format /var/stm/log/os/fpl.log.
PAGE 4
Report formats This section shows an example of each of the formats available, by keyword (k), raw hex ( r), text (t), or verbose PCA data (v).
PAGE 5
Keyword: BOOT_SCR_TEST_START Scratch RAM test Logged by: PA System Firmware PDC cabinet 0, slot 0, cpu 0 Data: 0x0000005600e00000 0x0000000000000000 Cause/Action: Forward progress, no action required Error Handling If the platform type cannot be determined by a scan of the log file, a generic platform type is used for event decoding. The -p command (described in the "Overall Interface" section) can be used to override the platform value and allow you to choose from a list of supported platforms.
PAGE 6
The Event Viewer is capable of decoding IPMI type E0 events (HP defined OEM record that allows event ID records to be passed through the IPMI) from the FPL files. Platform A particular Event ID means fundamentally the same thing on all platforms. However, some text (like cause/action) can vary. The Event Viewer will make an initial search of the FPL file to identify the platform type, then will use that information to decode the events.
PAGE 7
Standards/Guidelines/Policies/Conventions The textual version mimics the command set and report output from the Event Viewer available on the MP. Top of Page / http://www.hp.