JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Server Management Agents 2.1 User's Guide
search filter icon
search icon

Document Information

Preface

Documentation and Feedback

About This Documentation (PDF and HTML)

Change History

Oracle Server Management Agents 2. 1 User's Guide Overview

Oracle Hardware Management Agents

Installing Components Using the Oracle Hardware Management Pack Installer

Getting Started

Prerequisites

Installation Issues

Getting the Software

Installing Hardware Management Pack Components Using Installer

Configuring Hardware Management Agent and Hardware SNMP Plugins

Hardware Management Agent Configuration File

Configuring the Hardware Management Agent Logging Level

How to Configure the Hardware Management Agent Logging Level

(Solaris and Linux) Hardware Management Agent Runtime Options

Configuring your Host Operating System's SNMP

(Solaris and Linux ) Configuring Net-SNMP/SMA

How to Configure SNMP Gets

How to Configure SNMP Sets

How to Configure SNMP Traps

(Windows) Configuring SNMP

(Windows) How to Configure SNMP

Oracle Hardware SNMP Plugins

Overview of Oracle HW Monitoring MIB

Overview of Oracle HW Trap MIB

Overview of Oracle Storage MIB

Working With Management Agents

Retrieving and Setting Information Through SNMP

sunHwMonProductGroup

sunHwMonProductChassisGroup

sunHwMonSPGroup

sunHwMonInventoryTable

sunHwMonSensorGroup

sunHwMonIndicatorLocator

Generating SNMP Traps

Troubleshooting Management Agents

General Management Agents Troubleshooting

Solaris Operating System Troubleshooting

Linux Troubleshooting

Index

Configuring the Hardware Management Agent Logging Level

To configure the logging level, modify the hwagentd_log_levels parameter in the hwmgmtd.conf file. The hwagentd_log_levels parameter is a bit flag set expressed as a decimal integer. The following table explains the different logging levels that can be configured using the 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 troubleshooting

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


For example, when you want to set all logging levels between EMERG and NOTICE, the bit code values of all the required levels must be added and then converted to a decimal value. Referring to preceding table, the addition would be as follows:

0x0001 + 0x0002 + 0x0004 + 0x0008 + 0x0010 + 0x0020 = 0x003f

Converting this hexadecimal value to decimal equals 63, which is the desired log level. This is the decimal number that should be assigned to the hwagentd_log_levels parameter in the hwmgmtd.conf file.