iamt.rst 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101
  1. .. SPDX-License-Identifier: GPL-2.0
  2. Intel(R) Active Management Technology (Intel AMT)
  3. =================================================
  4. Prominent usage of the Intel ME Interface is to communicate with Intel(R)
  5. Active Management Technology (Intel AMT) implemented in firmware running on
  6. the Intel ME.
  7. Intel AMT provides the ability to manage a host remotely out-of-band (OOB)
  8. even when the operating system running on the host processor has crashed or
  9. is in a sleep state.
  10. Some examples of Intel AMT usage are:
  11. - Monitoring hardware state and platform components
  12. - Remote power off/on (useful for green computing or overnight IT
  13. maintenance)
  14. - OS updates
  15. - Storage of useful platform information such as software assets
  16. - Built-in hardware KVM
  17. - Selective network isolation of Ethernet and IP protocol flows based
  18. on policies set by a remote management console
  19. - IDE device redirection from remote management console
  20. Intel AMT (OOB) communication is based on SOAP (deprecated
  21. starting with Release 6.0) over HTTP/S or WS-Management protocol over
  22. HTTP/S that are received from a remote management console application.
  23. For more information about Intel AMT:
  24. https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
  25. Intel AMT Applications
  26. ----------------------
  27. 1) Intel Local Management Service (Intel LMS)
  28. Applications running locally on the platform communicate with Intel AMT Release
  29. 2.0 and later releases in the same way that network applications do via SOAP
  30. over HTTP (deprecated starting with Release 6.0) or with WS-Management over
  31. SOAP over HTTP. This means that some Intel AMT features can be accessed from a
  32. local application using the same network interface as a remote application
  33. communicating with Intel AMT over the network.
  34. When a local application sends a message addressed to the local Intel AMT host
  35. name, the Intel LMS, which listens for traffic directed to the host name,
  36. intercepts the message and routes it to the Intel MEI.
  37. For more information:
  38. https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
  39. Under "About Intel AMT" => "Local Access"
  40. For downloading Intel LMS:
  41. https://github.com/intel/lms
  42. The Intel LMS opens a connection using the Intel MEI driver to the Intel LMS
  43. firmware feature using a defined GUID and then communicates with the feature
  44. using a protocol called Intel AMT Port Forwarding Protocol (Intel APF protocol).
  45. The protocol is used to maintain multiple sessions with Intel AMT from a
  46. single application.
  47. See the protocol specification in the Intel AMT Software Development Kit (SDK)
  48. https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
  49. Under "SDK Resources" => "Intel(R) vPro(TM) Gateway (MPS)"
  50. => "Information for Intel(R) vPro(TM) Gateway Developers"
  51. => "Description of the Intel AMT Port Forwarding (APF) Protocol"
  52. 2) Intel AMT Remote configuration using a Local Agent
  53. A Local Agent enables IT personnel to configure Intel AMT out-of-the-box
  54. without requiring installing additional data to enable setup. The remote
  55. configuration process may involve an ISV-developed remote configuration
  56. agent that runs on the host.
  57. For more information:
  58. https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm
  59. Under "Setup and Configuration of Intel AMT" =>
  60. "SDK Tools Supporting Setup and Configuration" =>
  61. "Using the Local Agent Sample"
  62. Intel AMT OS Health Watchdog
  63. ----------------------------
  64. The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
  65. Whenever the OS hangs or crashes, Intel AMT will send an event
  66. to any subscriber to this event. This mechanism means that
  67. IT knows when a platform crashes even when there is a hard failure on the host.
  68. The Intel AMT Watchdog is composed of two parts:
  69. 1) Firmware feature - receives the heartbeats
  70. and sends an event when the heartbeats stop.
  71. 2) Intel MEI iAMT watchdog driver - connects to the watchdog feature,
  72. configures the watchdog and sends the heartbeats.
  73. The Intel iAMT watchdog MEI driver uses the kernel watchdog API to configure
  74. the Intel AMT Watchdog and to send heartbeats to it. The default timeout of the
  75. watchdog is 120 seconds.
  76. If the Intel AMT is not enabled in the firmware then the watchdog client won't enumerate
  77. on the me client bus and watchdog devices won't be exposed.
  78. ---
  79. linux-mei@linux.intel.com