Centos8-stream CIRA issue
Greetings. I'm currently experimenting with MeshCentral. I've created a cloud server and am fully able to use the agent capabilities for Windows and Linux. I'm also able to use the AMT CIRA capabilities for Windows 10. When I install the agent on Windows 10, I have the mesh group set up for fully automatic and it puts it in ACM mode and I get the AMT tab. Great.
The problem comes in when I use the same laptop, wipe Windows 10 (and also tried unprovisioning AMT via the ME boot screen), and then install Centos 8-stream -- when I run the agent, it works fine, but can't get it to recognize AMT or CIRA.
I can get it to work on LAN with MeshCommander.
So I tried a convoluted method -- I installed Windows 10, installed the agent, and got everything working. Then I wiped Windows and installed Centos8-stream -- but instead of wiping the mesh agent instance from the meshcentral, I kept it there. And then installed the agent again on Centos8-stream.
Now the result of this is that I have two mesh device instances -- one is the original one from Windows that doesn't recognize the agent (because it was obviously wiped). The CIRA does still work for this which is great. Then there's another instance which is just the agent -- which works fine too, but doesn't recognize AMT (see screenshot for clarification). So two instances for the same device, one CIRA, one agent.
So it's a convoluted way to use both the agent and CIRA for the same centos8 device. It works, but not ideal.
The long and short of it is for some reason the agent install (tried both the command-line and binary) for CentOS8-stream is not configuring the AMT so that it's recognized by meshcentral (as opposed to the Windows agent which seems to configure amt perfectly). I'm probably missing something or am just not familiar enough with AMT. Any help would be appreciated! Thank you, and awesome software!
Posted Jan 27, 2022, 4:35 AM UTC
You obviously know Intel AMT very well, nice!! The first thing I would check is if the MeshAgent on Centos8 can see Intel AMT thru the MEI driver. Almost all Linux distros come with "/dev/mei" or "/dev/mei0". Check if that is present in your OS.
Next, you can go in the agent "console" tab and type the "amt" command. That should return the current state of Intel AMT on that machine. See if that works.
Thanks for the reply! So Centos8-stream has /dev/mei0. When I went to the MeshCentral console for the agent instance and typed "amt", the response came back as "Intel AMT not detected". So it sounds like the agent is not communicating with the MEI driver for some reason? (which makes sense for why I could never get the AMT tab to show up)
FYI I tried installing the latest Ubuntu workstation and it works perfectly. Seems to be something about Centos8-stream not being able to communicate with AMT. Going to try Fedora next for comparison.
Tried Fedora 35 Workstation and it worked perfectly. Reinstalled CentOS8-stream and still having the same issue. The agent installs fine, but when I type "amt" in the console it returns "Intel AMT not detected."
I can access via MeshCommander on the local network however.
Tried with CentOS 8 (regular, not stream) and worked perfectly.
Also tried with CentOS 9 - Stream and works perfectly.
Seems to be limited to CentOS 8 - Stream for some reason...