When Intel AMT is configured for static IP addresses,then TWO IP address are required, one for the 'Host CPU' and the other for the 'IntelAMT Device'.
For example 'Host CPU' IP address of system is 192.168.0.9 and 192.168.0.101 is for 'Intel AMT device'. Is there any parameter that indicates that both these IP addresses are for the same system. Any such mapping information will be of help.
Help on this would be appreciated
Thanks & Regards,
It's my understanding that when using static addresses, both Intel AMT and the host OS must be set to the same address. This is because the network card only has one MAC address and so, if you set both to different addresses, the network will have two IP addresses with the same MAC and it's going to confuse other devices on the network.
Still, I have tried using separate IP addresses and yes, it works a little. You can ping AMT separately from the host OS, but it's not a supported or proper configuration.
In general, I recommend using DHCP, in my own lab; I use a Linksys WRTSL54GS with the DD-WRT (ddwrt.org) firmware. With that firmware, you can setup static DHCP mappings so that, the DHCP server will always give the same IP address to the same MAC address. I found that so much better than trying to change the Intel AMT settings & host OS settings.
Hope it helps,
Ylian (Intel AMT Blog)
Thanks for the question on the forum. You are correct that one must configure different IP addresses for AMT and host when operating with static IPs. Also your observation of two different mac addresses is correct.
When you configure thevPro machinewith static IPs, AMT will use the mac address called manageability mac which comes to play only in static IP mode. Manageability mac address is different from the mac address presented by the host.
Please make sure you give different names for AMT and host. Coming to your question about relating these parameters to same machine, as per the configured IP addresses and from the network point of view, these are two different machines. The only way to relate both of them to the same machine is by using the UUID. Both AMT and host should present you the same UUID as part of the inventory.
Hope this helps. Please let us know if you have further questions on this topic.
You are correct. In order to get the UUID from the host machine you need a software agent that can collect this andpresent itto a remote console.
Any particular reason why you would like to configure the systems in static IP mode?
For Issue1, You can get AMT network parameters using GetTcpIpParameters() API but unfortunately this API is not available for local interface. So it does not solve your purpose. Also in static IP mode, AMT dos not keep track of the host OS IP parameters.
For Issue2, I am assuming that you are trying to assign same IP address for host and AMT configured in static IP mode. If that is the case, it is not a valid configuration and you will have a IP address conflict since you have 2 systems with same IP address and different mac addresses. Also when you configure the static IP configuration, are you entering the default gateway information?
uuid_generate_time only helps in generating
new uuids, whereas we need to find out the
uuid of the system from linux.
When the intel AMT IP is queried, it provides
the uuid of the system. Similarly,
host IP running windows provides the
same uuid for the system. With this we can
map that both the IPs belong to the same system.
But, how do we do this for a AMT system
running with linux?"
Thanks & Regards,
As I mentioned in my previous post, if you set the same IP address for host and AMT, it is not a valid configuration and the results are not predictable. That is probably the reason you are seeing the issue of not being able to connect to any of them. Any particualr reason why you would like to set the same IP address for host and AMT, is this toavoid the issue of resolving the two ip addresses for the same PC?
Ajit has valid points.
There is one more possibility if you would like to do some coding. You can look into Intel SDK ZTPLocalAgent sample to interact with local Intel AMT driver to get Intel AMT LAN information and use Winsock to get Host OS LAN information and post the information to Event log. Intel Commander allows you to see the event log.
If you are chosing to go with static IP, you have to assign different IP addresses for host and AMT and have to map both of these IP addresses to a single system using UUID. I will discuss this further and let you know if there are any alternatives. I am sure you already know that if you use DHCP, then you do not have this problem.