0001 .. SPDX-License-Identifier: GPL-2.0
0002
0003 Intel(R) Active Management Technology (Intel AMT)
0004 =================================================
0005
0006 Prominent usage of the Intel ME Interface is to communicate with Intel(R)
0007 Active Management Technology (Intel AMT) implemented in firmware running on
0008 the Intel ME.
0009
0010 Intel AMT provides the ability to manage a host remotely out-of-band (OOB)
0011 even when the operating system running on the host processor has crashed or
0012 is in a sleep state.
0013
0014 Some examples of Intel AMT usage are:
0015 - Monitoring hardware state and platform components
0016 - Remote power off/on (useful for green computing or overnight IT
0017 maintenance)
0018 - OS updates
0019 - Storage of useful platform information such as software assets
0020 - Built-in hardware KVM
0021 - Selective network isolation of Ethernet and IP protocol flows based
0022 on policies set by a remote management console
0023 - IDE device redirection from remote management console
0024
0025 Intel AMT (OOB) communication is based on SOAP (deprecated
0026 starting with Release 6.0) over HTTP/S or WS-Management protocol over
0027 HTTP/S that are received from a remote management console application.
0028
0029 For more information about Intel AMT:
0030 https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
0031
0032
0033 Intel AMT Applications
0034 ----------------------
0035
0036 1) Intel Local Management Service (Intel LMS)
0037
0038 Applications running locally on the platform communicate with Intel AMT Release
0039 2.0 and later releases in the same way that network applications do via SOAP
0040 over HTTP (deprecated starting with Release 6.0) or with WS-Management over
0041 SOAP over HTTP. This means that some Intel AMT features can be accessed from a
0042 local application using the same network interface as a remote application
0043 communicating with Intel AMT over the network.
0044
0045 When a local application sends a message addressed to the local Intel AMT host
0046 name, the Intel LMS, which listens for traffic directed to the host name,
0047 intercepts the message and routes it to the Intel MEI.
0048 For more information:
0049 https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
0050 Under "About Intel AMT" => "Local Access"
0051
0052 For downloading Intel LMS:
0053 https://github.com/intel/lms
0054
0055 The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
0056 firmware feature using a defined GUID and then communicates with the feature
0057 using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
0058 The protocol is used to maintain multiple sessions with Intel AMT from a
0059 single application.
0060
0061 See the protocol specification in the Intel AMT Software Development Kit (SDK)
0062 https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
0063 Under "SDK Resources" => "Intel(R) vPro(TM) Gateway (MPS)"
0064 => "Information for Intel(R) vPro(TM) Gateway Developers"
0065 => "Description of the Intel AMT Port Forwarding (APF) Protocol"
0066
0067 2) Intel AMT Remote configuration using a Local Agent
0068
0069 A Local Agent enables IT personnel to configure Intel AMT out-of-the-box
0070 without requiring installing additional data to enable setup. The remote
0071 configuration process may involve an ISV-developed remote configuration
0072 agent that runs on the host.
0073 For more information:
0074 https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
0075 Under "Setup and Configuration of Intel AMT" =>
0076 "SDK Tools Supporting Setup and Configuration" =>
0077 "Using the Local Agent Sample"
0078
0079 Intel AMT OS Health Watchdog
0080 ----------------------------
0081
0082 The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
0083 Whenever the OS hangs or crashes, Intel AMT will send an event
0084 to any subscriber to this event. This mechanism means that
0085 IT knows when a platform crashes even when there is a hard failure on the host.
0086
0087 The Intel AMT Watchdog is composed of two parts:
0088 1) Firmware feature - receives the heartbeats
0089 and sends an event when the heartbeats stop.
0090 2) Intel MEI iAMT watchdog driver - connects to the watchdog feature,
0091 configures the watchdog and sends the heartbeats.
0092
0093 The Intel iAMT watchdog MEI driver uses the kernel watchdog API to configure
0094 the Intel AMT Watchdog and to send heartbeats to it. The default timeout of the
0095 watchdog is 120 seconds.
0096
0097 If the Intel AMT is not enabled in the firmware then the watchdog client won't enumerate
0098 on the me client bus and watchdog devices won't be exposed.
0099
0100 ---
0101 linux-mei@linux.intel.com
