search cancel

CAPM Data Aggregator karaf.log is cluttered with errors - ‘Unable to find device ItemID for component’

book

Article ID: 214463

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

The following messages are being continuously generated in the karaf.log on the DA:

ERROR | ory-thread-13104 | 2021-01-27 09:12:24,435 | nfigControllerRepositoryListener | nfigControllerRepositoryListener 1687 | .im.aggregator.discovery |       | Unable to find device ItemID for component 89414565 

Cause

This is a known defect concerning the VNA integration with CAPM which is fixed in DX NetOps CAPM version 21.2.1 and later releases.

Environment

DX NetOps CAPM 20.2 or later integrated with VNA.

Resolution

On the DR, in Vertica:

  1. cd /opt/vertica/bin

  2. Log into vsql:

    ./vsql -Udradmin -wdbpass (your password may vary)

  3. Run the following for a few of those itemIDs in the ERROR messages:

    select * from dauser.v_item_facet where item_id = ITEMID;

    select * from dauser.v_attribute_instance where item_id = ITEMID;

    \q to exit vsql

Example results:

dauser=> select * from dauser.v_item_facet where item_id = 89414569;
 item_id  | facet_id |                      facet_qname                       
----------+----------+--------------------------------------------------------
 89414569 |       63 | {http://im.ca.com/group}Group
 89414569 |       64 | {http://im.ca.com/group}GroupSupportedMetricFamilies
 89414569 |       65 | {http://im.ca.com/group}SyncableGroup
 89414569 |       97 | {http://im.ca.com/inventory}Pollable
 89414569 |      141 | {http://im.ca.com/sdn}SDN
 89414569 |      157 | {http://im.ca.com/sdn}ACIEndpointGroup
 89414569 |      167 | {http://im.ca.com/sdn}ItemSupportedMetricFamilies
 89414569 |      175 | {http://im.ca.com/core}Syncable
 89414569 |      179 | {http://im.ca.com/core}IPDomainMember
 89414569 |      796 | {http://im.ca.com/normalizer}NormalizedHealthScoreInfo
(10 rows)


dauser=> select * from dauser.v_attribute_instance where item_id = 89414569;
 item_id  |                      attr_qname                      | data_column  |  long_value   | float_value | string_value | byte_array_value 
----------+------------------------------------------------------+--------------+---------------+-------------+--------------+------------------
 89414569 | {http://im.ca.com/core}Item.CreateTime               | long_value   | 1615912204922 |             |              | 
 89414569 | {http://im.ca.com/group}SyncableGroup.GroupType      | string_value |               |             | aci_epg      | 
 89414569 | {http://im.ca.com/group}SyncableGroup.GroupItemFlags | string_value |               |             | 0            | 
 89414569 | {http://im.ca.com/inventory}Pollable.IsPolled        | long_value   |             1 |             |              | 
 89414569 | {http://im.ca.com/sdn}SDN.SdnID                      | long_value   |       9167356 |             |              | 
 89414569 | {http://im.ca.com/sdn}SDN.GatewayID                  | long_value   |      30037233 |             |              | 
 89414569 | {http://im.ca.com/core}Syncable.SyncID               | string_value |               |             | 29446296     | 
 89414569 | {http://im.ca.com/core}IPDomainMember.IPDomainID     | long_value   |       1646697 |             |              | 
(8 rows)

Here we see that these components are from VNA and we should not be making those calls for VNA components.

 

Attachments