none
Linux machine is showing grayedout in SCOM 2016 RRS feed

  • Question

  • Hi Experts ,

    I have installed scom agents in Linux (Redhat 7 and 6 ) machines , it installed successfully but showing grayedout in operation console of  SCOM 2016 

    Operation console :

    Can you please provide the possible reason and resolution of this gradeout issue.

    Thanks & Reagrds,

    Abhinash Kumar

    Tuesday, July 2, 2019 10:47 PM

All replies

  • Hello Abhinash,

    Sometimes it can take a while before they become Healthy/monitored, how long have you waited?

    Did you check the Operations Manager event log for any clues?

    Please also check the Health Explorer of the agents, click the bottom of the unit monitor in the left pane and check the state change events which can be found on the right side.

    Under the last state change event there should be more details, tell us what you find there and copy the error message here.

    Here are some common things that could cause grayed out linux agents:

    • Run As Account (ex: permissions, assignment to profiles...).
    • Issues with the agent certificates (ex: "issued to", "hostnames"...).
    • Issues with the account permissions (ex: sudo elevation) configured on the Linux agent side.
    • Issues with agent versions.


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, July 2, 2019 10:57 PM
  • Hi,

    Agree with Leon. Gray indicates communication problem. we may check if we access the agent computer via Secure SHell, using the username defined in SCOM RunAs account, as well as the SSH port.



    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, July 3, 2019 6:03 AM
  • Hello,

    You can check the winrm connectivity from all management servers in unix\linux resource pool for the exact error-

    winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Agent?__cimnamespace=root/scx -username:<UNIX/Linux user> -password:<UNIX/Linux password> -r:https://<UNIX/Linux server>:1270/wsman -auth:basic -encoding:utf-8

    Check below blog as well for verifying the steps followed for configuring scom agent on RHEL machines-

    https://kevinholman.com/2016/11/11/monitoring-unix-linux-with-opsmgr-2016/

    Also, verify sudoers file on RHEL machine according to below-

    https://social.technet.microsoft.com/wiki/contents/articles/7375.scom-2019-1807-1801-2016-and-2012-configuring-sudo-elevation-for-unix-and-linux-monitoring.aspx

    Wednesday, July 3, 2019 10:36 AM
  • Hi Alex,

    I am able to access Linux Machine from SCOM through SSH , using the same credential which used for installing scom agent , all required ports are open.

    Thanks & Regards,

    Abhinash Kumar

    Wednesday, July 3, 2019 4:44 PM
  • HI ,

    I run the above mentioned command get the below result :

    Please suggest .

    Thanks & Regards,

    Abhinash Kumar

    Wednesday, July 3, 2019 5:01 PM
  • It looks like the command due to the password perhaps?

    Try inserting the password within quotations:

    winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Agent?__cimnamespace=root/scx -username:<Linux user> -password:"<Linux password>" -r:https://<Linux server>:1270/wsman -auth:basic -encoding:utf-8

    Maybe then it will be the correct password and you will not get an access denied, nor a "is not a recognized as an internal or external command" error.



    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, July 3, 2019 9:51 PM
  • Hi,

    I have run the provided command it run successfully , below is its output :

    is this output is right , please review it and provide your valuable suggestion.

    Thanks & Regards,

    Abhinash Kumar

    Wednesday, July 3, 2019 10:10 PM
  • The output looks OK, it appears to work, have you tried shutting down the SCOM console and restarting it with the /clearcache parameter?

    "C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe /clearcache"


    If the agent is still grayed out, try running the following command:

    winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Agent?__cimnamespace=root/scx -username:<Linux user> -password:"<Linux password>" -r:https://<Linux system>:1270/wsman -auth:basic -skipCACheck -skipCNCheck -skiprevocationcheck -encoding:utf-8

    If the above command works, then you probably have a bad certificate on the agent.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, July 3, 2019 10:34 PM
  • Hi Abhinash,

    Thank you for the efforts made. Since we've checked the configuration and found no problems, if we try to re-install the agent of one of the problematic Linux computers, will it be green again?

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Thursday, July 4, 2019 6:44 AM
  • Hello, 

    How many management servers are in Unix\Linux resource pool?

    In case winrm connectivity is fine from all MS in unix\linux resource pool, could you check that the account is correctly mapped in Run as account and run as profile.

    Also, open health explorer and see if you find any monitor critical/warning.

    Thursday, July 4, 2019 9:00 AM
  • Hi Abhinash,

    As i could see those server gone grayed out from healthy. So I just want to check here how many MS you have in your Linux Resource Pool and are those MS added in Other Resource Pools too.

    Second thing how many Linux servers you have in your environment.
    Are those Grayed out server has something common pattern (Like Cloud VMs, On-prem Same domain VM etc.) 


    Cheers, Gourav Please remember to mark the replies as answers if it helped.

    Friday, July 5, 2019 8:24 AM
  • Hi Gourav,

    I have 10 MS and 8 GW servers in my environment , so I have 10 Resource Pool , In 2 Resource Pool I have 1 MS and in rest I have 2 MS  , 

    Currently I am Monitoring 6 Linux machine all are domain joined .

    Thanks & Regards,

    Abhinash kumar

    Friday, July 5, 2019 9:17 PM
  • Hi ,

    I checked all account is correctly Mapped in Run as Account and run as profile .

    In health explorer is doesn't show any error :

    Thanks & regards,

    Abhinash Kumar 

    Friday, July 5, 2019 9:22 PM
  • Hi ,

    I tried shutting down the SCOM console and restarting it with the /clearcache parameter  and also run above mentioned command it run successful .

    Can you please suggest how to check is these Linux machine has  bad certificate.

    Thanks & Regards,

    Abhinash Kumar

    Friday, July 5, 2019 9:25 PM
  • Hello,

    You can check the certificate on RHEL machine using below command-

    openssl x509 -noout -in /etc/opt/microsoft/scx/ssl/scx.pem -subject -issuer -dates

    Link-

    https://docs.microsoft.com/en-us/system-center/scom/manage-monitoring-unix-linux?view=sc-om-2019

    Monday, July 8, 2019 9:45 AM
  • Hi Abhinash,

    Alright, Count of VMs are not at all that much. Could you please check below blog and try to mimic this : -

    https://kevinholman.com/2016/11/11/monitoring-unix-linux-with-opsmgr-2016/

    And also do you have anything on MS' event viewer.


    Cheers, Gourav Please remember to mark the replies as answers if it helped.

    Tuesday, July 9, 2019 7:32 AM
  • Hi Abhinash,

    Yes, we can check the certificate using the openssl command mentioned above. If it is incorrect, we can change it via the following command.

    /opt/microsoft/scx/bin/tools/scxsslconfig -f -h <hostname> -d <domain.name>  


    In addition, for normal contidition, we can expand the Entity Health to see the details. As shown in the above screenshot, there is nothing to be expand. It seems the communication between the Linux computer and MS server is lost. If possible, we may consider re-installing the agent to see if it works.

    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Friday, July 12, 2019 6:40 AM
  • Hi,

    May we know the current status of the problem? Is there any other assistance we can provide?

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Friday, July 19, 2019 8:47 AM