search cancel

Number of MCS profiles deployed is smaller than the number of devices in the group and there are no failed or pending deployments

book

Article ID: 188999

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After deploying cdm MCS profiles to monitoring groups finding that the profiles all have missing server deployments that aren't listed as failures or pending on the Monitoring tab.  For example, the AIX Default Disk(s) profile says:

Application Status: Devices in group: 154.  profiles Deployed: 152.  Pending Profile Deployments: 0. Failed Profile Deployments: 0.

How can the 2 missing devices be found to troubleshoot them?

Cause

This can occur if robots were added to a monitoring group before the device was decommissioned.  After decommissioning the device was not deleted from the device tables in the UIM database.  When MCS profiles are then deployed to the monitoring group, the device is not available so the mon_config_service probe does not count these robots in the list where profiles are deployed.

Environment

Release : 9.2.0 or later

Component : UIM - MON_CONFIG_SERVICE v9.20 or later

Resolution

The following SQL query will provide a list of robots along with the name of the lowest level group the device is contained in and the MCS templates that were not deployed to it because it is not available:

SELECT

d.name AS device_name, d.status AS MCS_device_status,
dg.name AS GroupName, p.profileName AS MCS_ProfileName,
r.address AS robot_address, r.robot_active, r.status AS robot_status
FROM SSRV2device d
JOIN CM_GROUP_MEMBER gm ON gm.cs_id = d.cs_id
JOIN SSRV2DeviceGroup dg ON dg.cm_group_id = gm.grp_id
JOIN SSRV2Profile p ON p.group_id = dg.id
JOIN cm_device cd ON cd.cs_id = d.cs_id
JOIN cm_nimbus_robot r ON r.dev_id = cd.dev_id
WHERE d.status <> 'ok';

Note that this query will work for all MCS profiles for all probes.

To see only the MCS profiles associated with a specific probe (for example, the cdm probe), change the query to the following:

SELECT
d.name AS device_name, d.status AS MCS_device_status,
dg.name AS GroupName, p.profileName AS MCS_ProfileName,
r.address AS robot_address, r.robot_active, r.status AS robot_status
FROM SSRV2device d
JOIN CM_GROUP_MEMBER gm ON gm.cs_id = d.cs_id
JOIN SSRV2DeviceGroup dg ON dg.cm_group_id = gm.grp_id
JOIN SSRV2Profile p ON p.group_id = dg.id
JOIN cm_device cd ON cd.cs_id = d.cs_id
JOIN cm_nimbus_robot r ON r.dev_id = cd.dev_id
WHERE d.status <> 'ok'
AND p.profileName IN (select DISTINCT templateName from SSRV2Template where probe = 'cdm' and production = 1);

The output of these SQL queries would be similar to the following:

Additional Information

These SQL queries were only tested in MS SQL Server.  It may be necessary to consult a DBA to convert these to queries that will work in Oracle or MySQL.

Attachments