| Exit Print View | |
Sun Server Management Agents User's Guide |
|
About This Documentation (PDF and HTML)
Related Third-Party Web Site References
Introduction to Sun Server Management Agents
Sun Server Management Agents Features
Sun Server Hardware Management Agent
Sun Server Hardware SNMP Plugins
Sun Server Storage Management Agent
Sun SSM Component Manager Overview
(Linux and Solaris Operating Systems) Using Component Manager
(Linux and Solaris Operating Systems) Using Component Manager in Interactive Mode
(Linux and Solaris Operating Systems) Using Component Manager in Unattended Mode
(Windows Operating Systems) Using Component Manager
Configuring Hardware Management Agent and Hardware SNMP Plugins
Hardware Management Agent Configuration File
How to Configure the Hardware Management Agent Logging Level:
(Solaris and Linux Operating Systems) Hardware Management Agent Runtime Options
Configuring your Host Operating System's SNMP
(Solaris and Linux Operating Systems) Configuring Net-SNMP/SMA
(Windows Operating Systems) Configuring SNMP
(Windows Operating Systems) How to Configure SNMP
Sun Server Hardware SNMP Plugins
Overview of Sun HW Monitoring MIB
Sun Server Product and Chassis
Sun Server Hardware Monitoring MIB
Sun Server Hardware Management Agent
Sun Server Hardware Monitor Sensor Group
Working With Management Agents
Retrieving and Setting Information Through SNMP
Troubleshooting Management Agents
General Management Agents Troubleshooting
Solaris Operating System Troubleshooting
Differences in Hardware Management Agent SNMP Traps
Red Hat Installation Dependencies
Sun X6250 Server Module Wrong Service Processor Version Number
Gaps in sunHwMonInventoryGroup
SunHwMonInventoryTable Shows Incorrect Number of DIMMs
SunHwMonDiscreteHardDriveSensorTable Incorrect Sensors
Enterprise Field is Populated with Incorrect OID
ILOM 3.0 and Windows Server 2003 R2 Extended Data Mode Issue
Sun Blade X6450 with ILOM 2.0 and Windows Server 2003 Issue
Windows Hardware Management Agent snmpwalk on a Sensor Group Issue
Windows Hardware Management Agent SNMP Get Returns Empty String
Adaptec RAID Volumes not Reflected in ILOM CLI using Windows Storage Management Agent
Driver Errors in Windows Application Log
Ordering of Physical and Logical Disks Inconsistent Between Linux and Windows Storage Viewer
To configure the logging level, modify the hwagentd_log_levels parameter in the hwagentd.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.
|
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 hwagentd.conf file.
|
