NFA Bind Failure: Self reference

Products

• Network Flow Analysis

Issue/Introduction

When attempting to add NFA to NetOps Portal, you may run into a bind failure like this:

FromNetOps Portal DMService log:

Data source Network Flow Analysis@###.###.com encountered an error while processing a sync request.  The problem is in the data source, not NetOps Portal.  Check the logs for the data source to determine the cause of the problem.  The following stack trace shows the context of the sync request:

java.lang.IllegalArgumentException: Data source x is reporting x group self-reference(s).

        at com.ca.im.portal.dm.productsync.DataSourceBind.bindGroupMembers(DataSourceBind.java:1136)

        at com.ca.im.portal.dm.productsync.DataSourceBind.processBindingTables(DataSourceBind.java:187)

        at com.ca.im.portal.dm.productsync.DataSourceBind.bind(DataSourceBind.java:102)

        at com.ca.im.portal.dm.productsync.DataSourceBindPhase.executeInternal(DataSourceBindPhase.java:55)

        at com.ca.im.portal.dm.productsync.DataSourceSyncPhase.execute(DataSourceSyncPhase.java:95)

        at com.ca.im.portal.dm.productsync.BindSyncPhaseTask.execute(BindSyncPhaseTask.java:78)

        at com.ca.im.portal.dm.productsync.SyncPhaseExecutor$MakeDSSyncPhaseCallable$1.call(SyncPhaseExecutor.java:120)

        at com.ca.im.portal.dm.productsync.SyncPhaseExecutor$MakeDSSyncPhaseCallable$1.call(SyncPhaseExecutor.java:113)

        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)

        at java.util.concurrent.FutureTask.run(FutureTask.java:166)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)

        at java.lang.Thread.run(Thread.java:722)

Environment

NFA All Versions

Cause

This NFA instance was most likely added to another NetOps Portal at one point in time and the leftover groups are causing an issue.

**Before making changes we ask that you backup the reporter and netqosportal databases.**

 

Resolution

First we will need to locate the group that has a self-reference in NetOps Portal/NPC.

1. Putty/RDP to the NetOps Portal/NPC server and open mySQL from the command prompt by typing "mysql netqosportal -uroot -p".
2. To find the self reference type this command: 
   • Select * from bind_group_members where grouplocalid=childlocalid and childTypeName='GROUP';
3. Note the returned grouplocalid/childlocalid value(s). The 2 values should match each other.

The amount of rows returned should also match the amount of self-references in the bind failure error log. Now we need to remove them.

1. On the NetOps Portal server, run these commands:
   • Delete from bind_groups where grouplocalid=x;
     (Replace x with the grouplocalid of the returned values from the above select query for each group.)
   • Delete from bind_group_members where grouplocalid=x or childlocalid=x;
     (Replace x with the grouplocalid/childlocalid of the returned values from the above select query for each group.)
2. RDP to the NFA Console Server, and open mySQL from the command prompt by typing "mysql reporter -unetqos -pnetqos".
3. To delete the bad group(s), type this command:
   
   • Delete from groups where groupid=x;
     (Replace x with the grouplocalid/childlocalid returned value(s) from the above select query for each group.)
4. Initiate a 'Full Resync' from NetOps Portal and it should bind or move on to a new bind failure.