AMT stops responding via network - DHCP IP Address missing

[GMaie4]

Hello,

After initial Configuration on a new client AMT work fine. After some days AMT stops responding on the network. Only a hard reset of the computer pulling the powercord reactivate AMT on the client.

Since AMT Version 11 I have to change the AMT initial configuration  process.

Right now I enable AMT in BIOS. After reboot I logon to the MEBx via ctrl -P .   I change the default password and activate network access with DHCP Ip-Sharing with host. Thereafter I import my self-signed openssl certificates with powershell to access the system remote via port 16993 only.

That work fine but after a while AMT stops responding.  Connecting to AMT via localhost on the device revealed that the link is up but the system didn't receive an IP-address.

When I hard switch off the system MEBx reinitialize  and the system is working for a view days, loosing it s Ip -Address  again.

Solutions appreciate!

Regards

Günter

[jerrythea]

Here is the fixup script for Linux:

• sudo cp fixAMT.sh /usr/local/sbin
• sudo chmod 0740 fixAMT.sh

fixAMT.sh

#!/bin/bash
echo "Ensuring AMT Setting is correct at $(date)."
dev=$(lspci | grep -e 'Communication controller'|awk '{print $1}')
fulldev="0000:$dev"
cd /sys/bus/pci/devices/${fulldev}/power
pwd
ls -ls control
cur=$(cat control)
printf "Current Power Mode: %s\n" "$cur"
if [[ "$cur" != "on" ]]; then
printf "Setting to 'on'\n"
echo on >control
cur=$(cat control)
printf "New Power Mode: %s\n" "$cur"
else
printf "No Change Required.\n"
fi
echo "Done $(date)."

Here is the Linux systemd script:

• sudo cp FixAMT-vPro.service /etc/systemd/system
• sudo chmod 0640 /etc/systemd/system/FixAMT-vPro
• sudu systemctl daemon-reload
• sudo systemctl enable --now FixAMT-vPro

FixAMT-vPro.service

[Unit]
Description=Ensure valid AMT vPro Network Power Setting
Documentation=
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target

[Service]
Type=oneshot
ExecStart=/usr/local/sbin/fixAMT.sh
RemainAfterExit=yes

[Install]
WantedBy=network-online.target

• systemctl status FixAMT-vPro

● FixAMT-vPro.service - Ensure valid AMT vPro Network Power Setting
Loaded: loaded (/etc/systemd/system/FixAMT-vPro.service; enabled; vendor preset: disabled)
Active: active (exited) since ....
Process: 1359970 ExecStart=/usr/local/sbin/fixAMT.sh (code=exited, status=0/SUCCESS)
Main PID: 1359970 (code=exited, status=0/SUCCESS)
CPU: 28ms

Mar 09 09:45:00 ... systemd[1]: Starting Ensure valid AMT vPro Network Power Setting...
Mar 09 09:45:00 ... fixAMT.sh[1359970]: Ensuring AMT Setting is correct at ... 
Mar 09 09:45:00 ... fixAMT.sh[1359970]: /sys/bus/pci/devices/.../power
Mar 09 09:45:00 ... fixAMT.sh[1359979]: 0 -rw-r--r-- 1 root root 4096 ... control
Mar 09 09:45:00 ... fixAMT.sh[1359970]: Current Power Mode: auto
Mar 09 09:45:00 ... fixAMT.sh[1359970]: Setting to 'on'
Mar 09 09:45:00 ... fixAMT.sh[1359970]: New Power Mode: on
Mar 09 09:45:00 ... fixAMT.sh[1359970]: Done ...
Mar 09 09:45:00 ... systemd[1]: Finished Ensure valid AMT vPro Network Power Setting.

[wovka]

@jerrythea 

Thanks for the workaround and providing the script.

I am running VMware ESXi and need a workaround for this as the path "/sys/bus/pci/devices/" is not present in the OS? Does anybody have an idea how to apply the workaround on VMware ESXi?

Many Thanks

[jerrythea]

To completely close the loop and this, and provide some real good news to anyone monitoring this thread, Intel has finally resolved the issue via a bug-fix included in the latest 073 firmware update.

See the announcement here:

https://www.intel.com/content/www/us/en/support/articles/000093959/intel-nuc.html

Summary

How to work around the issue of Intel® vPro/Intel® AMT not responding.

Description

When trying to access Intel® vPro/Intel® AMT on the Intel® NUC 11 Pro - NUC11TN, Intel AMT will not respond.

This does not occur immediately. Instead it typically takes up to 24 hours for the Intel NUC not to respond.

Resolution

Update the BIOS to version 0073 or later.

Additional information

This issue may be seen when using Mesh Commander where Intel AMT will not respond after approximately 24 hours.

[jerrythea]

I have updated to this latest firmware, after removing my temporary FixAMT startup script.

The impacted NUC has been available via AMT for 3+ days now without issue.

[tanakakz_alpha]

I have a DELL OptiPlex 7080 with a 10th generation Core i5. My PC is still having issues similar to this thread, is Intel aware that this issue occurs on previous generations?

[jerrythea]

Best to file a support request.

Intel was actively engaged and assisted with the resolution.

It did take awhile to resolve, but they did reproduce and confirm the issue within a couple of weeks.