Users Guide

4. Close the file and restart all DSM services in the Services Microsoft Management Console.
Log Levels
Setting the log levels determines the range of message severity type you want to log. The following table
describes the log message severity levels that you can assign to LOG_LEVEL_MIN and LOG_LEVEL_MAX.
Severity Level Description
Trace Detailed information related to code flow.
NOTE: It is not recommended to set the
minimum log level to trace unless instructed
to do so by technical support.
Debug Detailed information that may be useful when
diagnosing problems.
Info Information related to operational events.
Warning An indicator that something unexpected happened
or an indication of some problem in the near
future. The software is still working as expected.
Typically, related to configuration or network
issues (time outs, retries, and so on).
Error A problem resulting in the software being unable
to perform some function.
Fatal A serious error, indicating that the software may
not be able to continue running.
Output Information that needs to be output in situations
where the logging system is not initialized.
By default, the minimum and maximum log message severity level are set to:
• LOG_LEVEL_MIN=info
• LOG_LEVEL_MAX=output
The default settings ensure that all messages with a severity of at least ‘info’ and at most ‘output’ are
logged.
Troubleshooting
Question: What do I need to do if all SNMP traps from an ESXi 5 host show up in OpenManage Essentials
as unknown?
Answer: You must change the hardware event source in the SNMP config on the ESXi 5 host from CIM to
IPMI. Run the following commands:
vicfg-snmp.pl --username root --password <yourpassword> --server <yourserver> --
hwsrc sensors
The output of the --show command would display the following:
Current SNMP agent settings:
289