Intel AMT Features > Discovery > Detailed Description

Detailed Description

The use cases in this section show how to discover the platform version and capabilities of an Intel AMT platform or a platform supporting Intel Standard Manageability. The discovery sample demonstrates all of these use cases.

Using RMCP Ping to Discover Platform State

The DASH Implementation Requirements (DSP 0232), published by the DMTF, specifies that a DASH-compliant platform should respond to a Remote Management and Control Protocol (RMCP) ping with an indication that the platform supports DASH. The ping message format and response are defined in the Alert Standard Format (ASF) Specification. Starting with Release 4.0, Intel AMT responds to an RMCP ping. The references to bytes that follow are the RMCP data in the response message.

In Releases 4.x through 5.0, Intel AMT responds to an RMCP ping with bit 5 of byte 9 set to true (according to DSP 0232 version1.0.0a).

In Release 5.1 and later, Intel AMT responds with bit 5 of byte 10 set to true (according to DSP 0232 version 1.1.0).

Release 6.0 adds additional information to the ping response:

   Byte 7 contains the firmware version: bits 0:3 contain the minor version; bits 4:7 contain the major version (for example, version 6.0 would be 0x60).

   Bytes 5 and 6 contain the open port: 16992: HTTP connections (no TLS); 16993: HTTPS connections (TLS enabled)

   Byte 8 provides the setup and configuration state of Intel AMT: 0x0: Not configured; 0x1: configuration in-process; 0x2 configuration completed.

In Release 6.1 or later, if the port is 0 (bytes 5 and 6 are 0), then the platform supports Intel AMT, but setup has not been performed. (This feature only works with a dynamic IPv4 address.)

In Release 7.0 and later releases, the ping feature also works when the host and Intel AMT are configured with a shared static IP address.

In Release 8.0, the ping feature does not work for the Intel Small Business Technology SKU.

Using the Setup Status to Discover Unconfigured Platforms

By sending an RMCP ping to all platforms, or a subset of them, in an enterprise, an IT organization can discover which platforms have been configured. If the platforms support Intel AMT Release 6.1 or later, IT can detect as-yet unconfigured Intel AMT platforms. The organization can then initiate configuration and check back via a ping to see if the process has completed.

The platform will respond to the ping only if the host network driver is up and is using a dynamic IPv4 address.

See Also:

   Use RMCP Ping to Determine the Platform State

 

Copyright © 2006-2013, Intel Corporation. All rights reserved.