Table 142. Log Mask Event Classes

 

 

 

Bit

Position

Logging Event Class

 

 

 

L

0

Logging Statistics (Class 0). Must be set. Event logging start and stop

 

 

times.

 

 

 

P

1

Protocol6specific information (Class 1). HP recommends that you do not

 

 

select this class unless your HP representative specifically asks that you do

 

 

so. This logging event class generates a multitude of log file entries.

 

 

 

M

2

Event messages (Class 2). HP recommends that you do not select this class

 

 

unless your HP representative specifically asks that you do so. This logging

 

 

event class generates a multitude of log file entries.

 

 

 

W

3

Warnings (Class 3), which indicate abnormal events, but do not necessarily

 

 

indicate subsystem problems. HP recommends that you do not select this

 

 

logging class.

 

 

 

E

4

Severe errors (Class 4), which indicate that NS6ARPA/1000 is not performing

 

 

as it should, but the subsystem was able to recover. HP recommends that

 

 

you select this logging class. NSINIT selects this logging class automatically.

 

 

 

D

5

Disasters (Class 5), which indicate that the NS6ARPA/1000 software detected

 

 

a severe and irrecoverable problem. HP recommends that you select this

 

 

logging class. NSINIT selects this class automatically.

 

 

 

R

6

Resource limit (Class 6), which indicates that a user6configurable resource

 

 

has been depleted. HP recommends that you select this logging class. The

 

 

network manager can use this information to adjust the node's configuration.

 

 

NSINIT selects this logging class automatically.

 

 

 

–

7

Reserved. Must be zero.

 

 

 

EVMON Output

EVMON writes log records to a file or device. EVMON output consists of an EVMON header and log records.

EVMON Header

Each time a user schedules EVMON, EVMON writes the following header to the log file or device:

currentTime

Event Log at nodeName

where currentTime is the system time at which EVMON was scheduled and nodeName is the name of the node at which EVMON is running and currentTime is the system time at which EVMON was scheduled. For example:

Tue Apr 8 1986 10:13:50 pm

Event Log at ANNE.LAB.HP1000

Maintenance Utilities 147