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

[pujeeth]

Hello VeeDub,

Greeting's!

Would request you to provide us the below information,

1. Can you confirm the firmware version of the AMT endpoints?
2. Are there any error messages or logs in the Event Viewer related to DHCP or network issues on the endpoint that is not obtaining an IP address?
3. Have you tried rebooting the endpoint that is not obtaining an IP address?
4. Can you provide the output of the following PowerShell command to check the network adapter status on the endpoint that is not obtaining an IP address?

Get-NetAdapter | Select-Object Name, Status, MacAddress, LinkSpeed

Best regards,

Pujeeth

Intel Customer Support Technician

intel.com/vPro

[VeeDub]

Hello Pujeeth,

> Can you confirm the firmware version of the AMT endpoints?

Working endpoints are using firmware v12.0.93 or v12.0.95

BBOX4 was on either v12.0.92 or v12.0.93 I upgraded as part of the troubleshooting to v12.0.95

> Are there any error messages or logs in the Event Viewer related to DHCP or network issues on the endpoint that is not obtaining an IP address?

No

> Have you tried rebooting the endpoint that is not obtaining an IP address?

Yes

I have worked out what the issue with BBOX4 is. After a restart AMT on BBOX4 obtains an IP address. And CIRA connects.

However, after the lease expires for the first time, the lease is not renewed.

I have no idea why.

With all the other hosts, the lease is being renewed.

> Can you provide the output of the following PowerShell command to check the network adapter status on the endpoint that is not obtaining an IP address?

Refer attached diagnostics.

I have replaced DR7 with DR3-3. Reason being, while both DR3-3 and DR7 are being served by the same DHCP Server, DR7 is on a different subnet to BBOX4.

DR3-3 is on the same subnet as BBOX4 so felt that it was a better comparison.

So the issue/question is: why is AMT on BBOX4 not renewing the DHCP lease?

BTW as mentioned previously I have noticed that in System Status the IP address is always reported as 0.0.0.0 even when I know via the DHCP Server what the actual IP address must be. The fact that Intel Active Management Technology / System Status always reports the IP address as 0.0.0.0 looks to be a bug. Can you report / escalate this?

[pujeeth]

Hello VeeDub,

Greetings!

Thank you for update, we would request you to share us the ECT logs from both the endpoints.

Steps to generate ECT logs are shared below:

1. Download the tool from the following link: Intel® EMA Configuration Tool
2. Installation:

• Download and unzip the tool.
• Double-click the .msi file and follow the installation prompts.

1. Run the Tool:
2. a. Open a command prompt as an administrator (or use Windows PowerShell*).
3. b. Navigate to the installation folder (default: C:\Program Files (x86)\Intel\EMAConfigTool).
4. c. Run the following command:
5. EMAConfigTool.exe --verbose

Regards

Pujeeth

Intel Customer Support Technician

Intel.com/vPro

[VeeDub]

Hello,

Logs as requested

[VeeDub]

Hello,

I have been comparing the two EMA logs.

What causes DHCP Mode to be Passive rather than Active?

[pujeeth]

Hello VeeDub,

Greetings!

Before we proceed, kindly let us know the details asked below:

1) Does both the endpoints belong to same endpoint group.

2) Are both the endpoints using the same AMT profile which is created in the Intel EMA console

3) Are both endpoints in company domain or out of band(remote)

Regards

Pujeeth

Intel Customer Technician Support

Intel.com/vPro

[VeeDub]

Hello,

1) Does both the endpoints belong to same endpoint group.

I'm not using EMA, I'm using MeshCentral

2) Are both the endpoints using the same AMT profile which is created in the Intel EMA console

N/A. See A1

3) Are both endpoints in company domain or out of band(remote)

Yes

[pujeeth]

Hello VeeDub,

Greetings!

Thank you for the below information,

Mesh-central is a open source tool please post your quire and they will assist you further.

https://www.meshcommander.com/meshcentral2

Regards,

Pujeeth

Intel Customer Support Technician

Intel.com/vPro

[VeeDub]

Hello,

I compared the two EMAConfig logs.

Can you tell me what causes DHCP Mode to be Passive rather than Active?

Or can you refer to me Intel AMT documentation where I can look for further information?

I have a number of endpoints that are working fine. My feeling is that this is an AMT issue with this endpoint rather than a MeshCentral issue.

Thanks

[pujeeth]

Hello VeeDub,

Greetings!

Kindly restart the endpoint that is not connected, then press Ctrl + P to access the MEBx. Navigate to the AMT Configuration menu and verify whether AMT is enabled.

Additionally, confirm whether both endpoints are within the company network or connected out-of-band (remotely connected ).

Regards

Pujeeth

Intel customer support technician

Intel.com/vPro

[VeeDub]

Hello,

AMT is activated in Admin Control Mode.

Both endpoints are within the company network.

[pujeeth]

Hello VeeDub,

Greetings!

Thanks for the update,

We would like to inform you that as the AMT has been enabled. kindly contact mesh-central for further assistance as it is out of our support boundaries.

Please find the link below, 

https://www.meshcommander.com/meshcentral2

Regards

Pujeeth

intel customer support technician

Intel.com/vPro

[pujeeth]

Hello VeeDub,

Greetings!

Please feel free to reply for further assistance.

Regards

Pujeeth

Intel customer support technician

Intel.com/vPro

[VeeDub]

Hello,

When AMT is not renewing DHCP lease, I fail to see how that is a MeshCentral issue.

That looks to me to be an AMT issue.

Nevertheless I'm considering by next steps.

As I mentioned, I've also noted that none of my systems (connecting via CIRA or not) display an IP address in Intel AMT System Status.

Do systems using EMA display an IP address in Intel AMT System Status?

Thanks

[pujeeth]

Hello VeeDub,

Greetings!

From the ECT logs, we observe that the IP address is displayed as 0.0.0.0. This behavior is by design. When configured with Intel EMA, the system identifies the endpoint using its MAC address (physical address), as this is a unique identifier.

As a workaround, if the endpoints are connected to the VPN please remove the endpoints from the VPN, and fully re- provision the affected endpoint using MeshCentral.

Additionally, if you plan to test with Intel EMA, please note that supported operating systems include Windows 10 and Windows 11.

This issue appears to be specific to MeshCentral. Since it is a third-party tool, we kindly suggest reaching out to the MeshCentral support team for further assistance.

Pujeeth

Intel Customer Support Technician

intel.com/vPro

[VeeDub]

Hello,

> From the ECT logs, we observe that the IP address is displayed as 0.0.0.0. This behavior is by design. When configured with Intel EMA, > the system identifies the endpoint using its MAC address (physical address), as this is a unique identifier.

Identifying the endpoint by MAC address may be by design, but if the 'server' be that EMA or 3rd party like MeshCentral is on a different subnet or even a different broadcast domain (i.e. physical network segment) then the AMT endpoint will need to use TCP/IP to contact the server.

When troubleshooting connectivity issues between the server and the endpoint, being able to confirm that the AMT endpoint has obtained an IP address is a key step.

My view is that the IP address being displayed as 0.0.0.0 is a bug and should be addressed.

If you disagree, can you advise how I can confirm what IP address the AMT endpoint has obtained?

Thank you

[pujeeth]

Hello VeeDub,

Greetings!

The Intel Active Management Technology (AMT) uses the same IP address assigned to the endpoint by the DHCP server as part of its configuration.

Best regards,

Pujeeth

Intel Customer Support Technician

intel.com/vPro

[VeeDub]

Hello,

Intel AMT allows remote management of the endpoint even if the OS on the endpoint is not loading / operational.

Therefore AMT cannot rely on the presence of an OS on the endpoint to obtain an IP address.

Once AMT has obtained an IP address, surely you can see that it makes sense for this IP address to be reported in System Status??

If the IP address is reported in AMT System Status, then it is clear what IP address AMT has obtained.

Or if AMT has not obtained an IP address (and 0.0.0.0 is reported), this fact is also clear, which makes troubleshooting straightforward.

You may recall, the reason that I opened this ticket was because AMT was not obtaining an IP address, but when I opened this ticket that fact was not apparent to me at that time - because the IP address being reported by System Status was 0.0.0.0

Regards

VW

[pujeeth]

Hello VeeDub,

Greetings!

We are checking on this issue and will get back to you with an update as soon as possible.

Regards

Pujeeth

Intel customer support technician

Intel.com/vPro

[pujeeth]

Hello VeeDub,

Greetings!

As per the ECT logs we see that affected endpoint shows that DHCP mode as passive, hence would request you to enable the DHCP and then share your observation.

For any further query please do hesitate to revert.

Regards

Pujeeth

Intel customer support technician

Intel.com/vPro