Page 56 - DCAP104_EXPOSURE_TO_COMPUTER_DISCPLINES

Unit 3: Using Operating System

The following table explains the different logging levels that can be configured using the Notes
various bit fields.

Log Level Bit Code Messages Logged

EMERG 0x0001 Information about the system being unusable
ALARM 0x0002 Information about any immediate action that must be taken
CRIT 0x0004 Information related to the Hardware Management Agent either
not starting or stopping because of critical conditions
ERROR 0x0008 Information related to the Hardware Management either not
starting or stopping because of critical conditions
WARNING 0x0010 Information about any conditions that generate a warning, which
do not stop the Hardware Management Agent
NOTICE 0x0020 Information related to normal functioning which is significant
INFO 0x0040 Informative messages about normal functioning
DEBUG 0x0080 Verbose debug-level messages, useful in troubleshooting
TRACE 0x0100 Highly verbose debug-level messages, useful in trouble-
shooting

Levels DEBUG and TRACE generate a lot of detailed messages and are
designed for troubleshooting. These levels are not recommended for
production usage.

3.6.3 How to Configure the Hardware Management Agent Logging Level

(a) Depending on the host operating system that the Hardware Management Agent is running
on, open the hwagentd.conf file from the path shown in the following table. You can use
any text editor to modify this file.
(b) Find the hwagentd_log_levels parameter and enter the decimal number calculated using the
instructions above.

(c) Save the modified hwagentd.conf file.
(d) Choose one of the following options to make the Hardware Management Agent reread the
hwagentd.conf file:
• On Linux and Solaris operating systems, you can manually restart (Solaris operating
system: refresh) the Hardware Management Agent, which forces the hwagentd.conf
to be reread. Depending on the host operating system that the Hardware Management
Agent is running on, restart the Hardware Management Agent.
• On Windows operating systems, you can restart the service using the Microsoft
Management Console Services snap-in.
The Hardware Management Agent rereads the hwagentd.conf file with the modified
hwagentd_log_levels parameter.

3.6.4 Configuring your Host Operating System’s SNMP
The Hardware Management Agent uses SNMP for network communications. For the Hardware
Management Agent to be able to use SNMP correctly on host operating systems, you must ensure
that SNMP is configured correctly. On Linux and Solaris operating systems, the snmpd.conf
file controls network access to the Hardware Management Agent. On Windows operating
systems the SNMP service controls network access to the Hardware Management Agent.

LOVELY PROFESSIONAL UNIVERSITY 49