Users Guide
Table Of Contents
- Dell Command | Monitor Version 10.2.1 User's Guide
- Introduction to Dell Command | Monitor 10.2.1
- Windows SMM Security Mitigations Table (WSMT) Compliance
- Standards and protocols for Dell Command | Monitor 10.2.1
- Use case scenarios using Dell Command | Monitor 10.2.1
- Using Dell Command | Monitor 10.2.1
- 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.2.1
- Managing Dell client systems remotely using Dell Command | Monitor 10.2.1
- Frequently asked questions for Dell Command | Monitor 10.2.1
- Troubleshooting steps using Dell Command | Monitor 10.2.1
- 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
b. Browse to WMI Control under Services and Applications.
c. Right-click WMI Control, and then click Properties.
d. Click the Security tab and select DCIM/SYSMAN under the Root tree.
e. Click Security.
f. Select the specific group or user that you want to control access and use the Allow or Deny check box to configure the
permissions.
6. Perform the following steps to connect to a WMI (root\DCIM\SYSMAN) on a system from a remote system using WMI
CIM Studio:
a. Install WMI tools along with wbemtest on the local system, and then install Dell Command | Monitor on the remote
system.
b. Configure the firewall on the system for WMI remote connectivity. For example, open the TCP ports 135 and 445 in
Windows firewall.
c. Set the Local Security setting to Classic - local users authenticate as themselves for Network access: Sharing
and security model for local accounts in the Local Security Policy.
d. Connect to the WMI (root\DCIM\SYSMAN) on the local system from a remote system using WMI wbemtest. For
example, \\[Target remote system IP Address]\root\DCIM\SYSMAN
e. Enter the Administrator credentials of the target remote system if prompted.
For more information on WMI, see the applicable Microsoft documentation at msdn.microsoft.com.
Installation failure on systems running Windows
If you are unable to complete Dell Command | Monitor for Windows installation, ensure that:
● You have Administrator privileges on the target system.
● The target system is a Dell manufactured system with SMBIOS version 2.3 or later.
● PowerShell console must not be open.
NOTE:
To check the SMBIOS version on the system, go to Start > Run and run the msinfo32.exe file and check for the
SMBIOS version in System Summary page.
NOTE: The system must be running supported Microsoft Windows operating system.
NOTE: The system has to be upgraded to .NET 4.0 or later versions.
BIOS setting enumeration value appears as 1
1. Verify that the following packages are installed with root user privileges;
● omi-1.0.8.ssl_100.x64.rpm
● srvadmin-hapi-8.3.0-1908.9058.el7.x86_64
● command_monitor-linux-<version number>-<buid number>.x86_64.rpm
2. If above packages are installed, then verify that the driver module is loaded.
a. Verify that the driver module is loaded by running the following command lsmod | grep dcdbas.
b. If the driver module is not available, retrieve the driver details by running the following command modinfo dcdbus.
c. Load the driver module by running the following command insmod <filename>.
Hapi installation fails due to the dependency of
libsmbios
If the installation fails due to dependency problems,
Force-install all dependent packages by running apt-get –f install.
28
Troubleshooting steps using Dell Command | Monitor 10.2.1