Users Guide
Table Of Contents
- Dell Command | Monitor Version 10.3 User's Guide
- Introduction to Dell Command | Monitor 10.3
- Windows SMM Security Mitigations Table (WSMT) Compliance
- Standards and protocols for Dell Command | Monitor 10.3
- Use case scenarios using Dell Command | Monitor 10.3
- Using Dell Command | Monitor 10.3
- Polling interval setting
- RAID status reporting
- Monitoring the Dell client systems
- Application log for Dell Command | Monitor for Linux
- Detecting advance format drives
- Boot configurations
- Changing the system settings
- Managing Dell client systems locally using Dell Command | Monitor 10.3
- Managing Dell client systems remotely using Dell Command | Monitor 10.3
- Frequently asked questions for Dell Command | Monitor 10.3
- Troubleshooting steps using Dell Command | Monitor 10.3
- Unable to remotely connect to Windows Management Instrumentation
- Installation failure on systems running Windows
- BIOS setting enumeration value appears as 1
- Hapi installation fails due to the dependency of libsmbios
- CIM resources not available
- Unable to execute the commands using DCM on the systems running Ubuntu Core 16
- Third-party licenses
- Other documents you may need
- Contacting Dell
● 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 file
available at /opt/dell/dcm/var/log.
Configuration file
You can update the configuration file 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 configuration file 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 configuration file. If the log level is set to DEBUG, the Dell Command | Monitor
application log will send all the information in to the specified log file.
NOTE: The default log level is set to INFO.
● File_Size — The user can specify the maximum size of the dcm_application.log file. The default file 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 file. If the default rollover count is 2,
the third backup file will override the oldest file.
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 configurations
NOTE:
Dell Command | Monitor for Linux does not offer the boot configuration capabilities. So this section is not applicable
for Dell Command | Monitor for Linux.
A client system can have one of two types of boot configuration:
● Legacy (BIOS)
● UEFI
In Dell Command | Monitor, the boot configuration (Legacy or UEFI) is modeled using the following classes:
● DCIM_ElementSettingData
● DCIM_BootConfigSetting
● DCIM_OrderedComponent
● DCIM_BootSourceSetting
● DCIM_SmartAttributeInfo
NOTE:
The terms Boot Configuration and Boot List Type are used interchangeably and convey the same meaning
representing Legacy or UEFI.
14 Using Dell Command | Monitor 10.3