Intel AMT Features > Discovery > Use Cases > Use RMCP Ping to Determine the Platform State
CollapseAll image

Use RMCP Ping to Determine the Platform State

The following steps use the RMCP ping response to determine the state of a platform with Intel AMT.

note-icon Note:

RMCP ping support for ProvisioningState and machine version is only from Intel AMT 6.0 and higher.


1.  Send an RMCP ping to the IP address of the platform under examination.

2.  If there is no response, the cause may be one of the following reasons:

a.   The platform is powered down or off the network.

b.   The platform does not support Intel AMT.

c.   The version of Intel AMT is earlier than Release 4.0, which was the first to support RMCP ping response.

d.   The version is release 4.0 or later but the platform is not yet set up. (Intel AMT Release 6.1 and later releases will respond to an RMCP ping  before setup is started or complete. The host must be active with a dynamic IPv4 address.)

e.   The version is release 4.0 or later and the platform is configured, but the RMCP ping response is disabled.

f.    The platform is Intel Small Business Technology, which does not support the ping feature.

3.  If there was a ping response, examine the values in the response:

a.   Examine bytes 1-4 for the IANA enterprise number: 343 (Intel Corp.)

b.   Examine byte 9 or 10 for DASH support:

   If bit 5 of byte 9 is true, then the platform supports DASH. (Intel AMT Releases 4.x and 5.0)

   If bit 5 of byte 10 is true, then the platform supports DASH (Release 5.1 and later releases, with the exception of the Intel Small Business Technology platform in Release 8.0.)

a.   Examine byte 7 for Intel AMT version (applies to Release 6.0 and later. In earlier Intel AMT versions this byte is always zero). If Byte 7 is not zero, bits 0:3 contain the minor version; bits 4:7 contain the major version (for example, version 6.0 would be 0x60). If Byte 7 is zero, and the Intel AMT version is 6.0 or later, the major version is specified in Byte 11 and the minor version is specified in Byte 12.

b.   Examine bytes 5 and 6 for the enabled port: 16992: HTTP connections (no TLS); 16993: HTTPS connections (TLS enabled) With Release 6.1 and later releases, if the port is 0, Intel AMT is present and awaiting setup.

c.   Examine byte 8, bit 0:1 for the  setup and configuration state: 0x0: Not configured; 0x1: configuration in-process; 0x2: configuration completed.

d.   Examine byte 8, bit 3 for the ports 16992 and 16993 state (supported from Intel AMT Release 6.0): 0x1: if both ports 16992 and 16993 are open; 0x0: otherwise.

Classes Used in This Flow


SDK Sample

If there is a sample demonstrating this flow, it is included in the SDK installation file. See SDK Installation Layout for details.

See Also:

   Detailed Description

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