Account Permission for SCOM monitoring on AIX servers

Question

In my SCOM 2016 UR9 environment, we have 450 Cross Platform servers where most of them are AIX servers. When I run the Processor performance data for yesterday's date, there is no data for 150 servers. I have verified these servers are healthy and not in maintenance mode.

There are some AIX servers for which data collection is not being collected regularly. It works for 2 days and not for a week/month.

Should I start looking at permissions on AIX servers? If yes, what permissions should be added in sudoers?

We use three service accounts for Unix Privilieged, Unix Action and Unix Maintenance. So, please guide accordingly.

Answer 1

Hi Diana,

You can use this for SCOM 2016:

Replace scxmaint & scxmon with your account used in SCOM, You can use a same account or 2 different account as well.

Example user configuration for Operations Manager 2016 agent v1.1

Example assumes users named: scxmaint & scxmon

Replace usernames & corresponding /tmp/scx-<username> specification for your environment

General requirements

These are any accounts you are using that use SUDO elevation including the Agent Maintenance account and or the monitoring account

Defaults:scxmaint !requiretty
Defaults:scxmon !requiretty

Agent maintenance

Agent maintenance for LINUX

Certificate signing

scxmaint ALL=(root) NOPASSWD: /bin/sh -c cp /tmp/scx-scxmaint/scx.pem /etc/opt/microsoft/scx/ssl/scx.pem; rm -rf /tmp/scx-scxmaint; /opt/microsoft/scx/bin/tools/scxadmin -restart
scxmaint ALL=(root) NOPASSWD: /bin/sh -c cat /etc/opt/microsoft/scx/ssl/scx.pem

Agent maintenance for UNIX

Certificate signing

scxmaint ALL=(root) NOPASSWD: /usr/bin/sh -c cp /tmp/scx-scxmaint/scx.pem /etc/opt/microsoft/scx/ssl/scx.pem; rm -rf /tmp/scx-scxmaint; /opt/microsoft/scx/bin/tools/scxadmin -restart
scxmaint ALL=(root) NOPASSWD: /usr/bin/sh -c cat /etc/opt/microsoft/scx/ssl/scx.pem

Install or upgrade

AIX

scxmaint ALL=(root) NOPASSWD: /usr/bin/sh -c sh /tmp/scx-scxmaint/scx-1.[5-9].[0-9]-[0-9][0-9][0-9].aix.[[:digit:]].ppc.sh --install ; EC=$?; cd /tmp; rm -rf /tmp/scx-scxmaint; exit $EC
scxmaint ALL=(root) NOPASSWD: /usr/bin/sh -c sh /tmp/scx-scxmaint/scx-1.[5-9].[0-9]-[0-9][0-9][0-9].aix.[[:digit:]].ppc.sh --upgrade --force ; EC=$?; cd /tmp; rm -rf /tmp/scx-scxmaint; exit $EC

Uninstall

Uninstall for LINUX

scxmaint ALL=(root) NOPASSWD: /bin/sh -c /opt/microsoft/scx/bin/uninstall

Uninstall for UNIX

scxmaint ALL=(root) NOPASSWD: /usr/bin/sh -c /opt/microsoft/scx/bin/uninstall

Log file monitoring

scxmon ALL=(root) NOPASSWD: /opt/microsoft/scx/bin/scxlogfilereader -p

Answer 2

Hi @Diana Shiny ,

while permissions needs to be verified, I don't thing that this is the cause here. Permissions are static in this case, meaning that it will either work or it won't. Still if you want to ensure you have configure the proper permissions, please do this here:

SCOM: Configuring sudo Elevation for UNIX and Linux Monitoring

What you can also do is check the Audit logs on some of your AIX systems, if there is an issue with the sudoers config, they should contain related records.

What you need to also do is to compare the time interval, when there is no data collected with the overall health of the systems - are those reachable and monitored, are there any other related alerts?
What you can also is to check whether the data is present in the DB at all:

SCOM SQL queries

Just run the performance data query and verify if there is data for the interval in question. If not there is some problem with collecting the data indeed, if Yes, there is most probably some issue with your report.

----------

Regards,
Stoyan