Devices Misidentified as Monitoring Points in DX NetOps Portal

Products

• Network Observability

Issue/Introduction

In DX NetOps Portal (Performance Management), several infrastructure devices—such as routers, switches, and load balancers—are incorrectly identified with a "Monitoring Point" context after the AppNeta Plugin was deleted. This misidentification prevents users from reporting on standard collected metrics like interface statistics, CPU, and memory.

Environment

 

DX NetOps (Performance Management: 24.4, 25.4.(1-4)

AppNeta Plugin.

 

 

Cause

A defect was identified where monitoring points created by the AppNeta VNA plugin are not automatically deleted from the database when the AppNeta engine is removed or the plugin is disabled. This can lead to overlapping IP addresses where a physical device’s IP (often in private or non-RFC1918 space) matches a previously assigned AppNeta agent address, causing the Portal to incorrectly merge or map the contexts.

Resolution

This issue is targeted to resolved in 25.4.5. The following workaround can be done to delete the monitoring point context:

1. Enable Write Access for iRep

 

• On the Data Aggregator, navigate to apache-karaf/etc/.

• Create or edit the file: com.ca.im.item.query.web.dao.QueryDaolmpl.cfg.

• Add the following line to the file: enableWrite=true.

• Save the file.

2. Access the iRep query tool in a web browser at: http://<DA_HOST>:8581/irepquery/

Search for the affected device by its ItemID (found in Portal or via REST):

SQL

select * from <ItemID>;

3. Synchronize Changes:

• Confirm the output shows the incorrect MonitoringPoint subtype.

• Run the following commands to clear the subtype and remove the facet:

  SQL

  update <ItemID> set Syncable.ItemSubType = [];
  update <ItemID> remove MonitoringPoint;

 4. Secure the iRep Tool.

Re-edit the com.ca.im.item.query.web.dao.QueryDaolmpl.cfg.

Set enableWrite=false

Save and Close the file.

The changes will be made after a sync of the data aggregator.