I have a strange situation with our latest added linux servers into scom. The network adaptor and heartbeat provider stays grayed out and also the server displays in grayed out. Everything else is monitored.
Try putting the server in Maintenance Mode for 30 minutes and see if it lights up after that
Looking at a Linux server in our SCOM I can see that the adapter and heartbeat are not monitored. In your case it seems rather strange.
Any other alerts related to this Linux server?
Try looking at the OperationsManager logs for the Management Server hosting the Linux server for warning/errors regarding your server. Also at the logs on the Linux server.
Maybe try to redeploy the agent on the server?
Is this happening to just this server? Is it a special version of Linux? Is it supported?
Sorry, dont know what could be wrong. I would open a case against Microsoft and see if they can help.
Support for 1801 ended 2019-08-08
To be frank, I don’t really know where the problem could be. In the past I have had issues with some specific linux version. In that case it was the SCOM agent that was the problem.
We have installed a complete new linux server with an older template RH7.4 and the result after adding the server to scom is the same. Everything will be monitored but is grayed out.
Any ideas about what can be the problem?
Your problem sounds familiar to me, but I can’t remember what the precise solution was.
I wonder if either your certificates are not in sync across all of your management servers (MS) or if you have a mix of SHA1/SHA256 certificates.
I would verify that certificates are in sync across all of your management servers and that you have only SHA256 certs (remove any SHA1 certs).
On the Linux agent, I would double-check that it’s using the correct certificate (SHA256).
In my travels, I’ve seen issues where monitoring starts healthy, then goes gray. For example, the discovery runs on MS1, and the agent is healthy. But at some point, control is shifted to another management server (MS2), and the agent goes gray because MS2 isn’t authorized to talk to the agent.
But you also mentioned that your monitoring is split (some healthy, some gray), so that has me wondering if your Linux Accounts are not correctly setup. As a test, use the same account in the Privileged and Unprivileged accounts. Some commands require elevation, and those might be failing.