Desktop Management Interface

Jump to: navigation, search


DMI is a protocol that permits to collect data from desktops and server and handle them in a central depository. Is very similar in scope to the SNMP protocol used to collect network data. Intel provied a personal computer implementation under LANDesk Client Manager brand. A good article that explains the protocol is available at

On HP-UX 11i, the DMI product has been superseeded by WBEM (Web-Based Enterprise Management). Nonetheless, you may obtain the old software components for HP-UX 11, 11i v1 and 11i v2 prior to September 2004 release at

There is a know issue on the DMI software component that may produce that dmisp process consumes 100% of cpu resources. If you need DMI for compatibility issues, you must update to version 4.0 of HP-UX DMI. Alternative, if your are not using DMI, you can remove DMI from your system and migrate to WBEM based administration.

Verified DMI version[edit]

You can use swlist to verified the current installed version of the product.

# swlist DMI
# Initializing...
# Contacting target "<hostname>"...
# Target:  <hostname>:/

# DMI                           B.11.11.40     Desktop Management Interface for HP-UX
  DMI.DMI-PRG                   B.11.11.40     DMI Software Development Tool Kit for HP-UX
  DMI.DMI-PRG-MAN               B.11.11.40     DMI Software Development Tool Kit for HP-UX Man Pages
  DMI.DMI-RUN                   B.11.11.40     DMI Runtime Environment for HP-UX
  DMI.DMI-RUN-MAN               B.11.11.40     DMI Runtime Environment for HP-UX Man Pages
  DMI.DMI-SHLIBS                B.11.11.40     DMI Shared Libraries for HP-UX
  DMI.DMI-SWCI                  B.11.11.40     HP-UX Software Distributor DMI Component Interface Daemon
  DMI.DMI-SWCI-MAN              B.11.11.40     HP-UX Software Distributor DMI Component Interface Man Pages
  DMI.DMI-UXCI                  B.11.11.40     HP-UX Standard Groups Component Instrumentation
  DMI.DMI-UXCI-MAN              B.11.11.40     HP-UX Standard Groups Component Instrumentation Man Pages

Uninstall DMI[edit]

If DMI is not been used by any product like ServiceControl Manager (SCM), System Configuration Repository (SCR) or System Insight Manager (SIM); DMI can be removed.

# swremove DMI

Disable DMI[edit]

The DMI automatically starting can be disable changing the variable "START_DMI" on the rc script configuration file /etc/rc.config.d/Dmiconfig.

This can be done directly editing the file or running the following command from the command line.

# ps -ef | grep -i dmisp
# /sbin/init.d/Dmisp stop
# ch_rc -l -p START_DMI ; ch_rc -a -p START_DMI=0 ; ch_rc -l -p START_DMI

Re-start DMI[edit]

Closing a DMI based management application like the SIM while it is actively retrieving information can leave the service provider in a locked state. This condition only occurs when the management application is closed with SIGKILL (-9) (Like opening SIM, opend DMI tool and closing the web page.

To recover from this condition, the service provider and associated component instrumentation processes must be reset by stopping DMI and then restarting it. This can accomplished by executing its rc control script with a 'stop' argument and then restarting it with a 'start' argument.

# /sbin/init.d/Dmisp stop
# /sbin/init.d/Dmisp start

DMI component don't start sucessfully on boot[edit]

Some success has been reported in addressing this issue when all 3 of the DMI components do not successfully start, as reported in the dmisp.log file.

  1. Save a back-up copy of the original start-up script /sbin/init.d/Dmisp
  2. Edit the start-up section of the /sbin/init.d/Dmisp script to change the sleep time.
-> /sbin/init.d/Dmisp

        # Start dmisp if necessary
        dmisppid=`ps -e |awk '$NF~/dmisp/ {print $1}'`
        if [ "X$dmisppid" = "X" ] ; then
                if [ "$START_DMI" -eq 1 -a -f /usr/dmi/bin/dmisp ] ; then
                        rm -rf /var/dmi/database/* > /dev/null 2>&1
                        rm -f /var/dmi/dmiPid /var/dmi/dmiReg > /dev/null 2>&1
                        export DMISP_DITIMEOUT=$DMI_TIMEOUT
--->                    sleep 10                                                        <--- Update sleep timeout
                        /usr/dmi/bin/Dmici start
                        # Echo appropriate message and return N/A
                        echo "Note: No DMI SP daemon configured for startup" 2>&1
                        exit 2 # N/A


3. Increasing the sleep value may avoid a timing problem where one of the components tries to start before the dmisp daemon is ready to provied connections. Usually a sleep value between 30 to 60 second is enough.

Superseed Product Notice[edit]

The DMI is replaced by WBEM. All new products, such as HP Systems Insight Manager (SIM) use WBEM instead of DMI to collect product state. To get the latest WBEM software available for your system check the following link.