Intel® AMT - Debugging

 

  1. The system is unresponsive and won't boot. How can this be resolved?
  2. Difficulties building the Sample Code.
  3. The USB key will not boot on the Intel AMT system.
  4. Why are we getting the following error while trying to run the sample code? ISVS_RegisterApplication returns 4103 (0x1007)PTSDK_STATUS_NETWORK_ERROR.
  5. Writing to the Intel AMT Storage (repeatedly): After a few successful writes, continuous write errors occurred for all subsequent writes. Reflashing the AMT memory did not help, but leaving the system on overnight did help. Why is this?
  6. Emulator Warning: "Cannot add username: admin and password admin to OS user accounts."
  7. Whenever an SOL session is opened using the IMRGUI, 100% of the CPU resources are taken.
  8. Hello packets are sent only when OS is on.
  9. When working in DHCP and setting a block-all policy in System Defense, after a certain amount of time AMT will be inaccessible.
  10. Intel SCS Exception: Cannot contact back AMT with IP:xxx.xxx.xxx.xxx Exception - Possible Reasons?
  11. When I use AMT IDE-R and SOL to boot a remote AMT client with a Linux rescue boot image, I can not receive any message through SOL after the image beginning to boot. Is there any Linux rescue boot image which can keep sending messages to SOL while booting?
  12. I have changed the default password on the AMT box from the default “admin”. Now,  When trying to use a USB key to provision an AMT box I am getting the following error:
    Intel® ME BIOS Extension login with default password failed
    Press any key to continue...
    2209 - USB Provisioning Error

 

  1. The system is unresponsive and won't boot. How can this be resolved?
    • • Unplug power cord, wait 20 seconds and try to boot the system again.
      • DIMM 0 must be populated with memory for AMT to work. AMT firmware is uncompressed and run in DIMM 0.
       
  2. Difficulties building the Sample Code.
    • • Check the readme file for any special instructions.
      • The sample code currently will not build with Microsoft Visual Studio* 2005. Try loading Microsoft Visual Studio* 2003.
      • Make sure the Platform SDK is installed.
      • Run the makewsdl.bat file - this batch file creates files that are needed in the build process.
      • Make sure the necessary directories have been added to the project (see the User's Guide.)
       
  3. The USB key will not boot on the Intel AMT system.
    • • USB boot partition needs to be 256MB or smaller.
      • Need to format USB key to be DOS bootable.
       
  4. Why are we getting the following error while trying to run the sample code? ISVS_RegisterApplication returns 4103 (0x1007)PTSDK_STATUS_NETWORK_ERROR.
    • Check to see if the Admin password has expired. If so, reset the admin user's password.
       
  5. Writing to the Intel AMT Storage (repeatedly): After a few successful writes, continuous write errors occurred for all subsequent writes. Reflashing the AMT memory did not help, but leaving the system on overnight did help. Why is this?
    • Flash write limits may have been exceeded. Optimize writes to see if this resolves the problem. Flash wear out protection is enforced by AMT to avoid permanent damage to flash by malware. Once the limit is exceeded, there is a time limit (40 minutes) that must be satisfied in order to write again.
       
    <
  6. Emulator Warning: "Cannot add username: admin and password admin to OS user accounts."
    • • The emulator is trying to add a user account to the machine with default credentials - username: admin, password: admin. If these do not meet credential restrictions set on the machine, they will have to be changed in the configuration file under the "Intel AMT Emulator\EmulatorCore" directory.
      • The emulator has not been validated on non-English Windows XP versions. If you run into problems with running the emulator on such OS, please change the “Language for non-Unicode programs” setting in Regional and Language Options to English (United States) as a workaround.
       
  7. Whenever an SOL session is opened using the IMRGUI, 100% of the CPU resources are taken.
    • For HyperTerminal to be working properly, IMRGUI is required. Check things like if Windows* firewall has been disabled or is blocking communication. IMRGUI should then start working once HyperTerminal is working properly.
       
  8. Hello packets are sent only when OS is on.
    • This is probably because Intel AMT is active only in S0 state. A configuration of the platform power policies in order to have Intel AMT communicate when the system is in Sx state (when the OS is not up) will have to be undertaken. See the MEBx screens and also the SetPowerSavingOptions() API.
       
  9. When working in DHCP and setting a block-all policy in System Defense, after a certain amount of time AMT will be inaccessible.
    • Root Cause:
      1. Every few minutes the ARP cache on a system is cleared.
      2. When in DHCP mode, when OS is up, AMT will not answer ARP requests because it relies on the OS to do so
      3. Because of the block-all policy – OS will not receive or be able to answer ARP requests
      4. Therefore – after the cache is cleared, MC will not be able to reach the AMT system due to ARP requests not being answered.

      Workaround
      When defining a block-all policy, make sure to define 2 extra filters.
      1. Pass Tx filter on Ethernet header for 0x806 (ARP)
      2. Pass Rx filter on Ethernet header for 0x806 (ARP)
      3. Make sure these filters are part of the policy.

      This will make sure that the host will answer ARP requests.
       
  10. Intel SCS Exception: Cannot contact back AMT with IP:xxx.xxx.xxx.xxx Exception - Possible Reasons?
    • Check the following possibilities:
      • The current password of the security key entered to the MEBx doesn’t match the MEBx password (most common reason).
      • Duplicate DNS registration (two host names bind the same ip) .
      • The SCS profile TLS PSK is configured to be plain text; the AMT machine doesn’t support this.
      • Or.... is there a security program running on the AMT system that might be blocking communication (also check the Firewall.... )
       
  11. When I use AMT IDE-R and SOL to boot a remote AMT client with a Linux rescue boot image, I can not receive any message through SOL after the image beginning to boot. Is there any Linux rescue boot image which can keep sending messages to SOL while booting?
    • The reason why the Linux boot image stop sending message to the SOL terminal could be that image isn't configured to send message to the serial console.
      And to enable the boot image to do so, we have to pass some parameters to the boot image when it begins to boot.
      More details please refer to this link:
      http://download.intel.com/support/motherboards/server/sb/solset pguide.pdf
       
  12. I have changed the default password on the AMT box from the default “admin”. Now,
    When trying to use a USB key to provision an AMT box I am getting the following error:
    Intel® ME BIOS Extension login with default password failed
    Press any key to continue...
    2209 - USB Provisioning Error 
    • The USB key method cannot be used once the password has been changed from the default “admin” password. For using the USB key in this scenario, You have to reset the password to admin by resetting the BIOS. 
       





 


Nähere Informationen zur Compiler-Optimierung finden Sie in unserem Optimierungshinweis.