SCOM Monitoring of Linux/Unix of Windows workgroup Agent with same name

Hello All!

Lets assume that for some reason you have in yours infrastructure servers which have exact same FQDNs but different IPs (sometimes it can happen with best of us). And you have question if it is possible to monitor such Objects with your SCOM. Every Entity in SCOM has its own unique HealthService GUID – according to this blog How are GUIDs in SCOM and SCSM calculated? such GUIDs calculated based on many parameter which are same inside Management Group and FQDNs for Windows  Computer and Unix/Linux Computer (which are same for our servers). So it is looks like we cannot monitor Servers with same FQDN.

Workaround available:

Imagine we have two servers deployed

– Server1

FQDN:ubuntu1.contoso.com

IP: XXX.XXX.XXX.001

– Server2

FQDN:ubuntu1.contoso.com

IP: XXX.XXX.XXX.002

On SCOM Management server we can create records in c:\Windows\System32\drivers\etc\hosts file

# Server1

#FQDN:ubuntu1.contoso.com

XXX.XXX.XXX.001 ubuntu1.contoso.com

# Server2

# FQDN:ubuntu1.contoso.com

XXX.XXX.XXX.002 ubuntu1-sec.contoso.com

Next on our “second” server we have to manually generate Certificate

/opt/microsoft/scx/bin/tools/scxsslconfig -h ubuntu1-sec.contoso.com -f -v

Now we can discover this server through SCOM Console with appropriate IP address.

Same can be done with Windows Server Computer but Certificate generated different way.

Happy Monitoring!

THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru AG IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.

OMS (Log Analytics) and Red Hat/CentOS integration issue

If you are trying to use Operations Manager Suite to monitor your Red Hat or CentOS VMs you will probably face following issue if you use “Connect” button on Log Analytics section in Azure:

5

There are two ways (tested on CentOS but it same behavior on Red Hat) to make it work:

 

First way:

  1. Disable Diagnostics for VM during creation

1

  1. Use connect button on portal.azure.com

2

  1. And after some time

3

And data will appear in OMS Logs.

Pros: That Workspace Connected on Azure Portal

Cons: Disabled Azure Diag (you’ll monitor VM with OMS  – so no need)

 

Second way:

 

  1. Deploy VM with Azure Diag Enabled:

4

  1. In order to enable OMS you’ll have to install agent Manually:

If previously you tried to use Connect VM button on Azure Portal and it was Fail: You have to use Disconnect button and wait until operation finished (VM have to be turned on.)

In Putty on VM

$> wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/v1.1.0-28/omsagent-1.1.0-28.universal.x64.sh

$> sha256sum ./omsagent-1.1.0-28.universal.x64.sh

$> sudo sh ./omsagent-1.1.0-28.universal.x64.sh –upgrade -w <YOUR OMS WORKSPACE ID> -s <YOUR OMS WORKSPACE PRIMARY KEY>

  1. At the End on azure portal in will be listed as Not Connected but monitoring and data in OMS should appear.

3

Pros But at the end you’ll both OMS data and Azure Diag.

Cons Not Connected in Azure Portal

 

Both ways should bring OMS Linux

If you deployed VM with Azure Diag Enabled and decided to disable it and use Connect Button in Log Analytics Section of Portal – it will NOT Fail if

5

You have to remove extension totally by running following commands:

> sudo rpm -e omsconfig
> sudo rpm -e omsagent
> sudo /opt/microsoft/scx/bin/uninstall

 

After that you Can use “Connect” feature)

Happy Monitoring 🙂

THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru AG IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.