1. Local Manageability Service
    1. Introduction
    2. Supported Hardware
    3. Building and installing the LMS
    4. Uninstalling the LMS
    5. Accessing the Intel AMT Device via LMS

Local Manageability Service

Introduction

The Local Manageability Service (LMS) allows applications to access the Intel® Active Management Technology (Intel® AMT) firmware via the local HECI interface. The LMS is dependent on the MEI driver. To use this make sure that the Intel® AMT Manageability Interface driver is installed and is connected to the firmware. The LMS service is meant to be run as a daemon. Messages from the service will be sent to the system log service (syslog). LMS messages will be marked with a source of "LMS".

Supported Hardware

  • LMS releases 2.x are supported on AMT 2.x systems only. (965 based systems)
  • LMS releases 3.1.x are supported on AMT 3.x systems (Q35 based systems)

Note that LMS does not work on systems with no Intel® Active Management Technology (Intel® AMT).

Building and installing the LMS

In order to build and install LMS, call "./configure" and then "make install". This builds the LMS daemon, installs it, and ensures that it will load upon startup.

Uninstalling the LMS

In order to uninstall the LMS first stop the service, either by distribution provided mechanism or by using "kill" command and then call “make uninstall”.

Accessing the Intel AMT Device via LMS

Once LMS is running, it listens for incoming connection requests on the ports 16992 and 16993. Each such connection request is passed via the Intel® AMT Manageability Interface driver to the AMT Device in the firmware, but only if the source IP address belongs to the local machine. Applications should use either the host name of the AMT Device (which can be the same or different than the host name of the machine), or the IP address of 127.0.0.1. Examples: 

http://127.0.0.1:16992
https://desktop:16993

Note that if the firmware is using a different IP address than the Linux machine (dedicated address) you cannot use this dedicated address to access the firmware via LMS. You must use the address 127.0.0.1 or the host name. This is because otherwise, the Linux routing layer will not know to forward such requests to LMS.

In case the firmware is using a dedicated host name (i.e. different than the one used by Linux), LMS should detect this and update the hosts file to indicate that the host name is an alias of 127.0.0.1. The host file can be found under the "/etc" folder (/etc/hosts).

Powered by WordPress. Theme by Bob