SD-WAN Aruba EdgeConnect Collector Troubleshooting Guide

This document provides a useful troubleshooting scenario for SD-WAN Aruba EdgeConnect Collector.

Troubleshooting

Device or Orchestrator populated with Partial Object synchronization

If the Device Onboarding process is not functioning as expected after the upgrade process, then check the spk import status in the MySQL database.

Navigate to SevOne NMS container.
```
nms
```
Execute the command below to perform database validation.
```
mysqlconfig
```

Execute the SQL command as shown below.


SELECT vendor, spk_file_name, 
       CAST(processed_status AS INT) AS processed_status, 
       CAST(active AS INT) AS active_int,
       processed_at 
FROM net.spk_data 
WHERE vendor = 'Aruba';

Verify the import status for the .spk files.

Example


+---------+-------------------------------------------+------------+------------------+------------+---------------------+
| vendor  | spk_file_name                             | import_val | processed_status | active_int | processed_at        |
+---------+-------------------------------------------+------------+------------------+------------+---------------------+
| Aruba   | ArubaEdgeConnect_Certification_v1.0.0.spk |          0 |                1 |          1 | 2025-06-09 10:36:07 |
| Aruba   | ArubaEdgeConnect_TopNViews_v1.0.0.spk     |          0 |                1 |          1 | 2025-06-09 10:36:08 |
+---------+-------------------------------------------+------------+------------------+------------+---------------------+
2 rows in set (0.001 sec)

Note: The processed_status should be set to 1, and the processed_at field should contain the UTC timestamp when the device was first discovered.

Note: For ArubaEdgeConnect_* .spk files where processed_at is 0 or null, manually import them using the following command.


/config/sdwan/Aruba

SevOne-import --allow-overwrite --file <spk_name>