SystemCenter

All about System Center Articles and Tutorials

DISCOVER UNIX / LINUX SERVERS IN SCOM

Posted by on Jul 21, 2016 in SCOM 2012

DISCOVER UNIX / LINUX SERVERS IN SCOM

Hello! Today I will show you how to discover UNIX / Linux server in SCOM and fix the most common error we face while discovery or managing the server.

First things first…. we need to make sure the version of UNIX / Linux server we are going to manager is supported by SCOM. You can get the list of supported UNIX / Linux OS version in SCOM from below URL:

https://technet.microsoft.com/en-us/library/hh212713(v=sc.12).aspx

Once we check the OS version in supported list, we can go ahead with the discovery wizard.

Please note, I assume that you have already prepared your SCOM environment for managing UNIX / Linux servers.

So, let’s start…

1. Load up the operations manager console and click on Administration.
2. Click on Discovery Wizard.

1

3. Select UNIX/Linux computers.
4. Click Next.

2

5. Under Discovery Criteria click on Add button.

3

6. Under Discovery Scope, click on Discovery Scope builder button.

4

7. Provide IP address of the servers to be discovered and click Save button.

Discovery can be done providing DNS host name and IP range as well, select option accordingly.

5

8. Click on Set Credentials button.

6

9. Select User name and password option.
10. Provide User name and password.
11. Select option This account does not have privileged access.
12. Click Apply and OK to continue.

7

13. Click on Save button to continue.

8

14. Select target resource pool and click Discover button.

I am selecting the resource pool which I created for UNIX/Linux monitoring.

9

Once the server is discovered, it will reflect under Manageable computers tab.

15. Click on Manage to continue.

10

Deployment will start and may take few minutes to complete.

11

If everything goes fine, you will get Successful status otherwise in few scenarios you may get Failed status due to Certificate issue. I have covered the troubleshooting part for Certificate issue at end of this post.

16. Click Done to close the Wizard.

12

Monitored server should reflect in healthy state with OS version under Unix/Linux Computers group after few minutes.

13

Troubleshooting:

As I mentioned above, the deployment may fail while certificate signing due to incorrect certificate. The deployment will stop with Failed status.

The common name (CN) which is used in the certificate must match the fully qualified domain name (FQDN) that is resolved by SCOM.  If the CN does not match, you will see the following error when you run the Discovery Wizard:

14

Below is the process to fix the same:

1. Login on Linux server using SSH client.
2. Check server hostname by running below command:

hostname –f

15

3. Make the host file entry on all the UNIX/Linux pool Management servers.

Example:

192.168.10.12     lim1.MX-ONE

We need to change the name on the certificate.

4. Run below command on Linux server:

/opt/microsoft/scx/bin/tools/scxsslconfig -f -v

16

If you get Error generating SSL certificate message as highlighted above, run below command:

sudo -s

After that run the command again:

/opt/microsoft/scx/bin/tools/scxsslconfig -f -v

17

This time you should get Conversion succeeded message.

5. Run the second command:

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

Now here you need to change the hostname and domain name on the certificate by using the –h and –d switches, as in the following example:

/opt/microsoft/scx/bin/tools/scxsslconfig -f -h lim1 -d mx-one

18

6. Restart the agent by running below command:

/opt/microsoft/scx/bin/tools/scxadmin -restart

19

7. Final Step..Run the discovery again. It should go through the Certificate Signing and Manage process.

20

Now the Deployment and Management should complete with Successful status.

8. Click Done to close the wizard.

21

After few minutes the server should reflect with green healthy check mark under UNIX/Linux Computers view.

22

Will cover how to prepare SCOM environment for UNIX/Linux monitoring in my next post.