Intel,Altiris Group

DHCP or Static IP for Intel® AMT? 

Jul 09, 2007 12:30 PM

Both dynamic and static IPs are supported by Intel® AMT clients, yet it is best that both the host operating system and ME (e.g. Intel® AMT Management Engine) use the same setting. Not all client environments use DHCP for IP addressing, thus both modes need to be supported.

Two MAC addresses appear for each Intel® AMT client. This is due to the host system and ME sharing the same physical network port, yet these could be viewed as separate systems.

How many IP addresses are needed? How many NETBIOS names are needed on the network? Do both IP addressing states support the same usage and functionality? The following points provide a brief summary between DCHP and Static environments. "Both" refers to the host operating system and ME.

  1. Both DHCP -- Only one (1) IP address is needed, with the hostname also shared. This state will support all Intel® AMT features and usage models.
  2. Both Static -- Two (2) IP addresseses are needed, with hostnames being unique. This state will not support enterprise provisioning\configuration, nor 802.1x, nor Intel® AMT over wireless.
  3. Mix of DHCP and Static -- This is not a supported and in some cases not allowed. If the host operating system is dynamic and the ME is static -- this state may work yet is not recommended.

Intel® AMT firmware in DHCP mode is able to request a lease. When the host system loads, Intel® AMT DHCP enters a passive mode and utilizes the host operating system IP address. During the system boot process, the ME will release it's assigned IP address and wait for the host operating system DHCP lease request sequence. (If you ping the target system, you will see a momentary pause in the ping responses). When the host system is off or unavailable, Intel® AMT DHCP switches to an active state. However, it will continue to utilize the IP address from the host operating system lease request

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.