search cancel

After adding a VNA plugin for velocloud, we got a bad device name, and the DA will not synch.

book

Article ID: 253721

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

Data Aggregator No Synchronize

After adding a velocloud plugin to VNA we added the gateway, and it caused the DA to stop synching.

We stopped the gateway, but it did not help.

Environment

Release : 22.2

Cause

A device name returned from velocloud was more than 100 characters,

100 characters is the table limit.

 

Error seen in DMService.log on pc:

CAPC encountered an error while trying to sync with data source Data [email protected]  The problem is in CAPC, not the data source.  The following stack trace shows the invalid SQL statement in CAPC:

org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [INSERT INTO dst_group (SourceID, UpdatedOn, `ItemSubTypeName`, `LocalID`, `ItemName`, `ItemDesc`, `Location`, `Latitude`, `Longitude`, `Elevation`, `SiteType`) VALUES (3,1667589483,'site','1233235','16169','',NULL,-9.543606,-37.745029,NULL,NULL),

(3,1667589483,'site','1233236','17491','',NULL,-17.820145,-42.117741,NULL,NULL),

ON DUPLICATE KEY UPDATE UpdatedOn=1667589483, `ItemSubTypeName`=VALUES(`ItemSubTypeName`), `LocalID`=VALUES(`LocalID`), `ItemName`=VALUES(`ItemName`), `ItemDesc`=VALUES(`ItemDesc`), `Location`=VALUES(`Location`), `Latitude`=VALUES(`Latitude`), `Longitude`=VALUES(`Longitude`), `Elevation`=VALUES(`Elevation`), `SiteType`=VALUES(`SiteType`)]; Data truncation: Data too long for column 'ItemName' at row 89; nested exception is com.mysql.cj.jdbc.exceptions.MysqlDataTruncation: Data truncation: Data too long for column 'ItemName' at row 89

The data was:

(3,1667589483,'site','1244464','EST RIO-DE JENEIRO, 4000 - KM 32 , Rio de Janeiro','',NULL,-22.853001,-43.547001,NULL,NULL),

(this has been edited to mask real info)

Resolution

Since DA was not synching, unable to use the VNA gateway view, so we used REST to identify and remove the bad gateway until the naming issue can be fixed:

curl -X GET http://YOUR-DA:8581/rest/sdngateways

Get the id from the results

curl -X DELETE -kv -u admin http://DA:8581/rest/sdngateways/<itemid from above>

Use this techdoc to tell when the cleanup is complete:

https://knowledge.broadcom.com/external/article/215841/how-do-i-know-when-a-dx-netops-virtual-n.html

then if needed, full resynch of DA.

Additional Information

Fix the naming issue before adding the gateway back in