Users Guide

For more information on SNMP, see Dell Command | Monitor SNMP Reference Guide.
• Dell Command | Monitor for Linux supports monitoring using WinRM and WSMan commands.
Application log for Dell Command | Monitor for Linux
Dell Command | Monitor for Linux segregates the application logs and alerts for reporting and debugging purpose. The history of the
generated alerts and logs for the Dell Command | Monitor application can be viewed in the dcm_application.log le available at /opt/
dell/dcm/var/log.
Conguration le
You can update the conguration le log.property available at /opt/dell/dcm/conf to apply the desired settings and DEBUG:
NOTE: Restart the OMI server after making any change in the conguration le to apply the changes.
• Log_Level — There are three log levels to segregate the system messages: ERROR, INFO, DEBUG
The user can change the log level from the conguration le. If the log level is set to DEBUG, the Dell Command | Monitor application
log will send all the information in to the specied log le.
NOTE: The default log level is set to INFO.
• File_Size — The user can specify the maximum size of the dcm_application.log le. The default le size is 500 MB.
NOTE
: The File_Size value must be expressed in bytes.
• BackupIndex — The user can specify the rollover count of the dcm_application.log le. If the default rollover count is 2, the third
backup le will override the oldest le.
Detecting advance format drives
Client systems are transitioning to Advanced Format (AF) drives for larger storage capacity and to address the limitations of 512-byte
sector hard drives (HDDs). The hard drives transitioning to 4KB sectors maintain backward compatibility, while the current AF hard drive,
known as 512e hard drive, match 512-byte SATA and operate at 4KB. During the transition, you may encounter performance issues such as
partition mis-aligned drives in the client systems resulting in failure of sector-based encryption software packages that handle 512e drives.
Dell Command | Monitor allows you to determine if the hard drive on a system is 4KB AF drive, which helps to prevent these issues.
Boot congurations
NOTE
: Dell Command | Monitor for Linux does not oer the boot conguration capabilities. So this section is not applicable for
Dell Command | Monitor for Linux.
A client system can have one of two types of boot conguration:
• Legacy (BIOS)
• UEFI
In Dell Command | Monitor, the boot conguration (Legacy or UEFI) is modeled using the following classes:
• DCIM_ElementSettingData
• DCIM_BootCongSetting
• DCIM_OrderedComponent
• DCIM_BootSourceSetting
• DCIM_SmartAttributeInfo
NOTE
: The terms Boot Conguration and Boot List Type are used interchangeably and convey the same meaning representing
Legacy or UEFI.
18 Using Dell Command | Monitor 10.1.0