The command line interface options are designed to be as similar as possible to the options for event log viewing on the MP.
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.
-x <hexevent>
Decodes a specific event by specifying the value as 2 64-bit
numbers.
-k|-r|-t|-v [<logentry>]
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.
-a <level>|-c<cell>
Filters options for cell number (c) or by alert level (a),
which may be one of the following:
0: Minor Forward Progress
1: Major Forward Progress
2: Informational
3: Warning
5: Critical
7: Fatal
For example, selecting an alert level threshold of 3
selects all events with alert levels of 3 or higher.
-p <platform>
Type of machine from which the events were generated. The
file will be scanned for this information if not entered.
Valid platforms are defined in the event dictionary library
and include the following:
hitachiserverha8500I
hp9000/785/C8000P
hp9000/800/rp3410P
hp9000/800/rp3440P
hp9000/800/rp3440#1P
hp9000/800/rp4410P
hp9000/800/rp4440P
hp9000/800/rp4440#1P
hp9000/800/rp7420P
hp9000/800/rp8420P
hp9000/800/SD16AP
hp9000/800/SD32AP
hp9000/800/SD64AP
hpservercx2600I
hpserverrx1600I
hpserverrx1600I
hpserverrx2600I
hpserverrx2620I
hpserverrx4640I
hpserverrx5630I
hpserverrx5670I
hpserverrx7610I
hpserverrx7620I
hpserverrx8610I
hpserverrx8620I
hpsuperdomeserverSD16AI
hpsuperdomeserverSD32AI
hpsuperdomeserverSD64AI
hpworkstationgx4000I
hpworkstationzx1600I
hpworkstationzx2000I
hpworkstationzx6000I
hpworkstationzx8000I
IntelMPServerI
NECserveru32000I
NOTE: This list will only display if you enter an incorrect platform
type when using the -p command.
-f <file>
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.nn
The command line Event Viewer installation directory from the EIT bundle is:
HP-UX:
\opt\smstools\bin
Windows:
C:\Program Files\Hewlett-Packard\EIT\opt\bin
HWE Releases
The command line Event Viewer installation directory from the HWE bundle is:
/usr/sbin/diag/contrib/slview
Example command menu in a paged session:
Welcome to the FPL (Forward Progress Log) Viewer 1.2
The following FPL navigation commands are available:
D: Dump log starting at current block for capture and analysis
F: Display first (oldest) block
L: Display last (newest) block
J: Jump to specified entry and display previous block
+: Display next (forward in time) block
-: Display previous (backward in time) block
<cr>: Repeat previous +/- command
?: Display help
q: Exit viewer
The following event format options are available:
K: Keyword
R: Raw hex
T: Text
V: Verbose
The following event filter options are available:
A: Alert level
C: Cell
U: Unfiltered
SL (<cr>,+,-,?,F,L,J,D,K,R,T,V,A,C,U,q) >
This section shows an example of each of the formats available, by keyword (k), raw hex ( r), text (t), or verbose PCA data (v).
23 SFW 0,2,0 0 0x04000a1020e00000 0x00ffff02ffffff94 BOOT_SYNC_CELLS_START 24 SFW 0,2,0 0 0x030008e320e00000 0x0000000000000004 BOOT_GET_CONFIG_SET 25 SFW 0,2,0 0 0x04000a4f20e00000 0x00ffff02ffffff94 BOOT_CELL_RENDEZVOUSING 26 SFW 0,2,0 0 0x030009a520e00000 0x0000000023c34600 BOOT_PD_RENDEZ_DELAY 27 SFW 0,2,0 0 0x0400085720e00000 0x00ffff02ffffff94 BOOT_CONFIG_SET_RENDEZ 28 SFW 0,2,0 0 0x04000a4e20e00000 0x00ffff02ffffff94 BOOT_CELL_RENDEZVOUSED 29 SFW 0,2,0 0 0x0300084020e00000 0x00000000001e8480 BOOT_CELL_SYNC_DELAY 30 SFW 0,2,0 0 0x0300083a20e00000 0x0000000000000004 BOOT_CELL_LOCAL_RENDEZ_SET 31 SFW 0,2,0 0 0x0300084020e00000 0x00000000001e8480 BOOT_CELL_SYNC_DELAY 32 SFW 0,2,0 0 0x030009c920e00000 0x0000000000000004 BOOT_RENDEZ_SET_CREATED
0x0200086420e00000 0x0000000000000105 0x0200086020e00000 0x0000000000000000 0x0200086220e00000 0x0000000000000010 0x0200086120e00000 0x0000000000000000 0x0200086320e00000 0x000000002cb41780 0x030008e020e00000 0x0000000000000004 0x030008e120e00000 0x0000000000000000 0x040009be20e00000 0x00ffff02ffffff94 0x040009a120e00000 0x00ffff02ffffff94 0x3480083720e00000 0x000000000002000c
Log Entry 44: Alert Level 3: Non-Critical Keyword: HP-UX_DUMP_WRITE_ERROR OS dump, error writing image area to disk (E055) Logged by: HP-UX cabinet 0, slot 0, cpu 0 FRU Physical Location: 0x000000ffff07ff83 FRU Source = 8(I/O device) Source Detail = 3(local bus adapter) Cabinet Location = 0 Card Cage Location = 0 Backplane Location = 0 I/O Slot Number = 7 0x0400035500e00000 0x000000ffff07ff83 Log Entry 45: Alert Level 1: Major Forward Progress Keyword: HP-UX_HEX_RUN_CODE OS legacy PA hex run code (Fxxx) Logged by: HP-UX cabinet 0, slot 0, cpu 0 Legacy PA HEX Chassis Code = 0xcf02f 0x3f00033a00e00000 0x00000000000cf02f
Log Entry 314: Alert Level 3: Non-Critical Keyword: BOOT_ROM_REV_TO_FIT_REV_WARNING Rom revision not equal to FIT revision Logged by: PA System Firmware PDC cabinet 0, slot 0, cpu 0 E0 Event Timestamp: Wed Feb 26 18:22:46 2003 0x6b00025900e01760 0x010000003e5d7676 Cause: A ROM Rev and FIT Rev do not match. Action: Update ROM, if problem persists contact your HP representative for support. Log Entry 315: Alert Level 0: Minor Forward Progress 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
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.
In the command line interface, submission of the incorrect type of file, missing files, etc. are handled as syntax errors. If a specified input or output file cannot be opened, both the Windows and HP-UX versions generate an error message and the viewer terminates.
The following messages result in the Event Viewer exiting with an error:
Indicates the FPL log file specified for decoding could not be opened.
Indicates the XML database file could not be opened.
EIT releases:
Windows:
The database export file is located at C:\Program Files\Hewlett-Packard\EIT\var\data\eventdef
HP_UX:
The database export file is located at /var/smstools/data/eventdef
HWE releases:
The database export file is located at /var/stm/data/eventdef
If known, the reason for the failure will be displayed in the message; for example, "file not found".
This section lists and describes, in detail, each function and feature of the completed product as seen by the user.
The purpose of the Event Viewer is to allow field engineers to navigate the event logs from systems that use IPMI over a longer span of system operation time on the SMS or any HP-UX machine which has the required dictionary, database data file, and system event log files.
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.
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. If a platform cannot be determined, 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.
The object of the command line interface for the Event Viewer is to provide the same information as is available on the MP, in the same format, using the same navigational operations. In addition, Problem-Cause-Action (PCA) detailed reporting, not available on the MP, is added to the design.
The following navigation commands are available:
F: Display first (oldest) block
L: Display last (newest) block
J: Jump to specified entry and display previous block
D: Dump log starting at current block for capture and analysis
+: Display next (forward in time) block
-: Display previous (backward in time) block
<cr>: Repeat previous +/- command
?: Display help
q: Exit viewer
The following event format options are available:
K: Keyword
R: Raw hex
T: Text
V: Verbose <- new for the SMS Event Viewer
The following event filter options are available:
A: Alert level <level>
C: Cell <cell number>
U: Unfiltered
In the command line interface of the Event Viewer, a verbose (full descriptive) report of the entire event log could be extremely large. In a paged command line session, this is not an issue, but before the user sends a verbose report to the screen, they need to be aware of the potential for extensive load on disk and memory resources used to buffer the output.
The command line interface runs in the DOS command shell on Windows 2000 and in a shell window on HP-UX. The program, including database export file and directory structure is installed via the mechanism used for the EIT bundle as defined by the SMS software release planning team, typically a CD. In addition, this tool is a part of the OnlineDiag bundle installed with HP-UX releases.
The textual version mimics the command set and report output from the Event Viewer available on the MP.