AMT configured for DHCP but not obtaining an IP address

[VeeDub]

Hello,

I have two AMT endpoints on the same subnet, both configured for DHCP, one endpoint is obtaining an IP address from the DHCP server and one isn't currently (although it has previously).

I'm wondering if there is some option equivalent to ipconfig /renew that I can execute on the endpoint that doesn't have an IP address to force it to request an address.

Or is there some tool that I can use to run diagnostics?

In the screenshots, DR7 is the endpoint that has obtained an IP address (you can see this by reviewing the list of leases on the DHCP Server) while BBOX4 has no lease.

Apart from that all the configuration appears identical and I note that in System_Status both endpoints report an IP address of 0.0.0.0

From my experience, all AMT endpoints report an IP address of 0.0.0.0 rather than the address that has been obtained from the DHCP server?

Thanks

VW

[VeeDub]

Hello,

If you look at the topic subject:

AMT configured for DHCP but not obtaining an IP address

AMT Network settings attached

[pujeeth]

Hello VeeDub,

Greetings!

Kindly allow us sometime, we are checking with our internal team and will get back to you with an update as soon as possible.

Regards

Pujeeth

Intel customer support technician

Intel.com/vPro

[VeeDub]

Hello,

What I have done with this endpoint, is that I have configured the DHCP server to provide an infinite DHCP lease to the AMT endpoint.

The DHCP server responsible, services a number of other AMT endpoints without issue.

For some unknown reason, with this particular endpoint, it will obtain an IP address after a restart, but when the DHCP lease expires the AMT endpoint then fails to renew the lease.

From a troubleshooting perspective, what I would like (and what really should be available already) is the ability to determine what IP address AMT currently has.

To me the obvious answer is to have System Status to display the current IP address rather than 0.0.0.0

I'm aware from your previous comments that the 0.0.0.0 is "by design". Frankly the logic behind that decision is crazy IMO and that should be reviewed (and hopefully changed).

However if displaying 0.0.0.0 (really useful!) remains the product teams preference, then there needs to be another way of being able to determine what IP address AMT is currently assigned. 

I had to work out what was going on with this endpoint by trial-and-error and observation, this troubleshooting would have been vastly simplified by having a way to directly report the current IP address assigned.

Thanks

VW

[pujeeth]

Hello VeeDub,

Greetings!

We have replicated the issue with our internal setup and have confirmed that the same IP( 0.0.0.0) which is seen in our setup as well, hence this is working as per design.

Regards,

Pujeeth

Intel Customer Support Technician

intel.com/vPro

[VeeDub]

Hello,

I understand from your previous comments that what I am observing is as per design.

What I'm trying to explain to you is that the design is flawed and should be changed.

There needs to be a way to identify what IP address AMT is using, particularly when AMT is configured for DHCP.

Regards,

VW

[pujeeth]

Hello VeeDub,

Greetings!

Thank you for the update. We will share this information with our developer team so they can review it. If any fixes are required, they will be included in a future update.

We will proceed to close this case. If you find that you still required assistance, we kindly request you to respond to the case. This will allow us to either reopen the current case or initiate a new one.

Regards,

Pujeeth

Intel Customer Support 

intel.com/vPro

[miniture768]

When one of your AMT endpoints is not obtaining an IP address from the DHCP server while the other on the same subnet works fine, it's likely due to an issue specific to the endpoint or its network configuration. Here’s how to troubleshoot and resolve the issue:

---

1. Verify AMT Configuration

• Access AMT Settings: Use the Intel Management Engine BIOS Extension (Ctrl+P during boot) to enter the AMT setup menu.
• Check Network Settings: Ensure the endpoint is still configured for DHCP. If it's set to static, switch it back to DHCP.

---

2. Reset the Endpoint

• Perform a power cycle: Shut down the machine completely, disconnect the power cable (and battery, if applicable), wait for a minute, and reconnect.
• If the issue persists, reset the AMT configuration to factory defaults and reconfigure it for DHCP.

---

3. Inspect the Network Connection

• Physical Connection: Verify that the network cable or adapter is functioning properly. Swap the cable and port with a known working one.
• Link Status: Check if the Ethernet port’s LEDs are active (indicating a physical connection).
• If using Wi-Fi, ensure the SSID and credentials are correctly configured in AMT.

---

 

[AlHill]

@miniture768   And, if this does not work, get chatgpt to fix their answer.

Doc (not an Intel employee or contractor)
[Fear and the desire for control are primary motivators for shadow dwellers. ]