Enhancement request : IP address assigned to AMT to respond to ping

[VeeDub]

Hello,

I have recently experienced a few issues with AMT.

I have noticed that the IP address assigned to AMT by DHCP does not respond to ping.

From a troubleshooting perspective it is better if an IP address does respond to ping.

Can you submit this as a request to the product development team?

Thank you.

VW

[vish1]

Hello VeeDub,

Greetings!!

Could you please share a screenshot of the issue for further investigation? This will help us better understand the situation and assist you more effectively.

Best Regards,

Vishal Shet P

Intel Customer Support Technician

intel.com/vpro

[VeeDub]

Hello,

I am using MeshCentral to manage AMT endpoints in CIRA / Admin-mode.

Recently I have had endpoints going offline in MeshCentral (refer screenshot - latest example DR4-5).

According to the DHCP Server the endpoints have an IP address, but as the AMT endpoints do not respond to ping, it is impossible to know if the AMT endpoint's TCP/IP stack is responding.

Through trial-and-error I have established that if I perform a power-drain on the AMT endpoint this will resolve the behaviour (Perform a power cycle: Shut down the machine completely, disconnect the power cable for 1 minute).

However this is a very poor work-around.

All of the CIRA endpoints are remote to me and to perform a power drain I need to be on-site with the endpoint.

I want to troubleshoot why the AMT endpoints are going offline.

After further investigation in this latest instance DR4-5 has not obtained an IP address from the DHCP Server. What would cause this to occur?

And how can I force DR4-5 to try and refresh the IP address without a power drain?

I have also observed multiple examples where according to the DHCP Server, the AMT endpoint does have an IP address and in those examples so far the only "solution" is to perform a power drain on the endpoint.

For the reasons mentioned above, performing a power drain is a very poor work-around.

I need a way of resolving these issues that doesn't require a site visit or better still not have the issues occur in the first place.

I think the underlying problem may be a recent BIOS update. All of these systems were stable until the last 1 - 2 months when there have been a number of BIOS updates released.

Thanks

VW