I have setup ME in bios, with IP Add: AAA.BBB.CCC.25, KVM, SOL, IDE is all on.
Host OS is setup with IP: AAA.BBB.CCC.26
I have connected through VNC viewer, AMT KVM works fine and I can see OS without any problem. When I restart OS using shutdown option in OS, Ping starts failing for AAA.BBB.CCC.25-- fails untill OS reboot!!
I thought ME/AMT's IP address should respond even though OS is down?
Please help... I am trying to figure this out sinc last couple of days!!
What tools\method did you use to configure the platform?
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?
Based on your video, looks like you are using different IP's for ME and Windows, that is the reason you are facing this behavior.
You should use the same IP address and it should works as expected.
Thanks in Advance!
First of all, Bruno is incorrect. When using dynamic IP addresses, AMT share's an IP with the OS. However, for static AMT 6 and before MUST use a different IP address from the OS. So, your configuration with dual, static IPs is correct. As a side note, AMT 7 supports the same static IP in AMT as the OS. For more info on static IPs in AMT see http://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm?tur... this link.
Second, I tried to reproduce this in my lab but was not able to. I used 2 static IPs next to each other and I did not fill in a default gateway for DNS server in AMT (just as in the earlier video). For me, pings continue (with a loss of 1 or 2) and KVm stays connected. So, we need to get very specific about versions, configuration, and steps taken. Here's what I have:
Lenovo Think Centre M90p (5536) (read from sticker on system)
BIOS Version: 5jkt40uas (read from BIOS POST screen
AMT Firmware: 6.0.2-build 1194 (read from AMT web UI)
LAN Driver: e1k62x64.sys - v184.108.40.206 (read from device manager on the listed file)
I am configured using Digest crednetials (admin) and no TLS. I configured locally in MEBx.
My Console has XP 32 (sp3) and is on the same subnet at AMT. AMT system has Win7 64.
If you can provide me with more details, I can try again to reproduce the issue. Or, you may try changing your setup (EG new BIOS, new LAN driver) to see if you can get it to work. Please let me know what you find.
First of all, please forgive me for my english
Written will be a lot, and I hope the case
But all that you read will be translated by Google, and manually edit my.
As the saying goes, "From Russia with love :-)
***If moderater a hand in bringing in a readable message - thanks to him!
I took two computer based on motherboard ASUS P7Q57-M DO
first - in June 2010
second - March 2011
In the process of setting up the first IP-KVM - no problems there was no
When you set up the second - thought go crazy
did everything the same, but as it should work - not working
First of all, Bruno is certainly not right about the fact that the IP-address to the ME and the OS should be the same.
I'm sorry, but this is nonsense.
Madness is over after the following actions:
1) In the BIOS option "APIC ACPI SCI IRQ" - was set to "Enable"
(In the BIOS of ASUS P7Q57-M DO this option present)
There is a relationship or not - I do not know (I forgot to put it right )
2) installation old drivers, from June 2010
you can download here - http://files.mail.ru/7H3A85 http://files.mail.ru/7H3A85 (342 Mb)
After completing these two items, I have everything working correctly.
***is below - leave for Russian users
Я собирал два компа, на базе материнской платы ASUS P7Q57-M DO
первый - в июне 2010 года
второй - март 2011 года
В процессе настройки первого в части IP-KVM ни каких проблем не было
При настройке второго - думал сойду с ума
всё делал одинаково, но так как должно работать - не работает Прежде всего, Bruno конечно же не прав по поводу того что IP-адреса на ME и в OS должны быть одинаковы.
Прошу меня простить, но это абсурд. Всё закончились после следующих действий:
1)В BIOS параметр "APIC ACPI SCI IRQ" - был установлен в "Enable"
(в BIOS ASUS P7Q57-M DO такой параметр есть)
Есть взаимосвязь или нет - не знаю (забыл поставить сразу)
2)Установленны старые драйвера от июнь 2010 года
скачать можно отсюда - http://files.mail.ru/7H3A85 http://files.mail.ru/7H3A85 (342 Mb)
Intel_Chipset_V9111020_XPVistaWin7 После выполнения этих двух пунктов, у меня всё заработало нормально. Удачи.
Unfortunately, the AMT 7 manuals is not correct and I already request development team to update.
Before ME 4.0, OEM had the ability to set a different MAC address to AMT and host using AMTNVMCustomize tool. In such a case, they should also use different IP and this mode was called "dedicated MAC". In "Shared MAC" that is available since ME 4.0 (where AMT dedicated MAC was left "FF"), ME uses the host MAC, hence, in DHCP they must have the same name and in static IP they may still use the same IP address or different.
Just to summarize: if you have ME 2 and 3, you must use different IP addresses while with ME 4 and beyond you can set the same IP address or different.
From network standpoint, while you are using the same host and ME name with different IP address can be a problem for DNS update and make the machine unreachable
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
I am still having same exact issue that you are having.
I think, Moderator from Intel should get involve and confirm bug , so we don't go crazy finding solutions.