”
2
| : |
2
| ( | : |
¤ The command line can also help you simulate automatic analysis with the following commands. ( ï ca msg -auto eventLogFile – simulates automatic analysis for a single binary event log file (see Chapter 5). ( ca msg -autoall eventLogFileDir – simulates automatic analysis for all the binary event log files in a directory (see Chapter 5).
2
| ( | : |
/ By default, Compaq Analyze excludes correctable events (those with an event type of 620 or 630) from the translation output. If you want to see all the events in the binary event log file, add the command modifier for your syntax: ( o ca x trans showall ( A ca n translate all
2
| ( | : |
‡ Commands that specify filters automatically consider all the events in a binary event log file. Therefore, if you use a filter, correctable events that are normally ignored will be displayed unless you explicitly filter them. The following common syntax filter statement will remove correctable events from the output: ( K filter "entry_type!=620,630"
In order to help you control the processing of correctable and uncorrectable events, the following filtering keywords are supported by the common syntax Entry_Type filter.
¢ If you are using the new common syntax, the following keywords perform the same function.
2
| ( | : |
Ï In addition to overriding the service obligation, you can also change the existing obligation or rerun the service obligation installation script. In order for your service obligation changes to take effect, you must stop and restart the director once your changes are complete. Refer to Chapter 1 for more information on stopping and restarting the Director.
2
| ( | : | e
c‡ To change your service obligation enter the following command: n( B desta servob change 2
a: When you change your obligation, the information about your current obligation is presented followed by prompts where you can enter new information. The following example shows the information and prompts presented along with sample answers:
" e WEBES Obligation Change= / g
e ----------------------- s g
e ; p
aC Service Obligation change date: Mon Mar 27 14:11:34 MST 2000f G G
., Service Obligation current state: Valid I t
(C Service Obligation current start date: Mon Mar 27 00:00:00 MST 2000
B f =
"O Service Provider Company Name: Compaq d "
S Service Provider Employee Name: Jack Smith >
rU Service Provider Employee ID#: 000000000000 o = n
.x Please enter new service obligation start date <dd-mmm-yyyy>: 28-MAR-2000 < w
hc Please enter service obligation term end date: 28-MAR-2001 o = n
.G Service Obligation term: 1 years, 0 days, 0 hours, 0 minutes, 0 secondsv o c
u r s
= Is this correct [y]: a >
Ñ If you enter incorrect information, enter no at the final prompt to redisplay the prompts.
T .
p2
| U | A(: | E
=è You can also update the service obligations settings by running the installation script again. To run the installation script again, use the following command: /( C desta servob install a y m
iÒ The prompts that appeared during installation are shown again. The following example shows the prompts presented and the default answers:
i 2# WEBES Service Obligation Validationa i t
a# ----------------------------------- / M
" - Z
s, Please input service provider name [COMPAQ]: l r
T6 Please input system/subsystem serial number [1234567]: o n
fC Is the Service Obligation number the same as the serial number [y]:" L
ID Please enter the start date of the current obligation [28-Mar-2000]: N
E& Service Provider: COMPAQ E
A' System/subsystem serial number: 1234567D R L
=' Service obligation number: 1234567i 2 u
r+ Service obligation start date: 28-Mar-20002 t
t Is this information correct [y]: g d
O2
| ( | : | =
bÇ You can use the CLI to view the FRU tree associated with a binary log file. The syntax for viewing the FRU tree is as follows:
I #
8 ?
h o u e
t
f2
| D | (: |
36 Specifying an input file generates the first FRU tree for that file. If you do not specify a binary event log, the system's FRU tree is shown. See Section 2.9.1 for more details on specifying an input file.
S
2
| / | =(: | a
eˆ An example of an entry from the generated output is shown here:
O B <==== NODE_FRU_DESC - -
& ====> NODE_FRU_DESC FRU Version 6.0 E
c$ ID: 0xb680 (NODE_FRU_DESC) 1 2
$ Parent: 0xb340 (NODE_FRU_DESC) r e
t$ Next: 0xb580 (NODE_FRU_DESC) a e
:$ Prev: 0xb780 (NODE_FRU_DESC) E
B E
y N_Type 21 C <
B8 N_Sbtyp 29 Power Supply u
N N_Size x0100 E
e! Hd_extension x0000 0000b 0 F
>+ Owner_Handle_V6 x0000 0000 0000 0000s l t
F+ Current_Owner_V6 x0000 0000 0000 0000O O O
"+ Node_ID xF002 FFFF 0281 FFFFd O "
<+ Node_Flags x0000 0000 0000 0200F " v
rev 0
I change_counter 0E F
+ Config_Handle_V6 x0000 0000 0000 0000M " N
=+ Affinity_Handle_V6 x0000 0000 0000 0000 c
+ Parent_Handle_V6 x0000 0000 0000 B340O =
B+ Next_Sibling_Handle_V6 x0000 0000 0000 B580> T
. Previous_Sibling_Handle_V6x0000 0000 0000 B780 a e
+ Child_Handle_V6 x0000 0000 0000 0000/
U+ FW_Usage x0000 0000 0000 0000 a e
t+ OS_Usage x0000 0000 0000 0000 l r
i Checksum 0l m N
P Magic GLXY = N
d b
> A 7
n! diag_flag x0000 0000a u a
l! diag_failure_info x0000 0000e d u
O FRU_manufacturer -E n
t FRU_model -" - -
/ FRU_part_number -F " /
FRU_serial_number -p e
E FRU_firmware_revlevel -E l t
n
:2
| t( | : | "
O1 All the event frames supported by the event decomposer service are listed in a binary file installed with Compaq Analyze. The decomposer reads this binary file when translating binary events. By default, the binary file is saved as: E( { installed_directory/desta/data/KnowledgeStore.dat T 1
E
/³ The list of event frames is derived from the Java classes contained in the supplied *Knowledge.jar files.
=
N¾ If necessary, you can rebuild the the KnowledgeStore.dat file. The file might need rebuilt for the following reasons:
e¸ If you need to rebuild the KnowledgeStore.dat file using the current .jar files, execute the following command: B( ; desta bldknw
D
²
=