ME operation is board dependent. What board are you using?
What tools\method did you use to configure the platform?
Access the target AMT system's WebUI using http://AAA.BBB.CCC.25:16992
What version of AMT is noted at the end of the Copyright line. In the example above, the AMT version is 5.2.10-build 1023.
Under the Network Setting option on left, ensure "respond to ping" is enabled.
Next - click on the Power Policies option. Curious which policy is selected for your system.
One last item - what is the ping response TTL? Should be either 128ms or 255ms.
Look forward to your answers.
I have Lenovo- MP90P-B1U mother board , I assume, it havs Q57 Express chipsets.
For power option it is setup for ON -- Desktop on So, S3, S4-5
I am using Managebility commander tools, ,Real VNC Viewer plus for KVM
I am using real VNC Plus, I am rebooting it through Windows OS Shutdown/reboot option-- Not from Managebility commander tools.
This is an AMT 6.0 system.
Per your earlier notes - it sounds like the KVM session remains intact through the reboot - correct? Only the ping response fail - correct?
Wired or wireless network?
Does the response never come back?
There will be an interruption in the ping response during reboot - this is due to the active\passive nature of the network interface. The hand-off between the operating system and the management engine will vary. In some cases, it could be up to 2 minutes.
If the system is powered down and ping responses fail - check the Idle timeout value in the MEBx. An issue I've seen in the past on AMT 6.x systems is the management engine goes to sleep and it may take ~20 seconds before it wakes-up and is able to respond.
Have you talked with Lenovo support about this issue?
Did you mark "Respod to Ping"
If it is marked, ME and Windows can be using different IP addresses, can you confirm?
My two cents!
Your reply was rejected by a moderator. Please edit your reply and resubmit it for approval.
it is Lenovo M90P, I assume, it hae Q57 Express Chipsets motherboard.
I have Lenovo M90P B1U, I asusme, it has Q57 Express Chipsets.
It is different IP.
Do the ping responses resume within 30 seconds or less?
You must match IP addresses in order to works properly
I also have this bug
I think it's driver problem, or some of its parameters
If in the OS disable a network interface - this problem disappears
and AMT is working correctly, Shutdown/reboot OS - it does not matter
What do you think about it?