Network Management

Aruba Edge Connect interface is appearing properly, but interface traffic is missing or blank in SolarWinds Platform 2024.2.1 and below

The article provides information about an issue where Aruba (Silverpeak) edge devices are discovered, and polling data is occurring via API. In some scenarios, the device interface appears, but data related to interface traffic is missing, blank, or incomplete. When testing via SNMP directly to Aruba, all interface traffic is being reported properly.

First published date

12/23/2024 3:02 PM

Last published date

2/16/2025 5:32 PM

Overview

Interfaces for Edge devices polled by Aruba Orchestrator aren't polled properly as expected, and no data is shown related to them.

In the Collector log, the following error message may appear with SD-WAN exception code of TUNNELS_STATISTICS_POLLING_FAILED OR UPLINKS_POLLING_FAILED :

 

ERROR SolarWinds.Orion.SdWan.Collector.ProcessingStage.TunnelsStatisticsPollerResultPreprocessor - 
N.SdWan_TunnelsStatistics.REST.Aruba poller result for Node X. Info: Failed, Error message: 
Failed to poll Aruba SD-WAN Edge with Device ID X.
SD-WAN Exception code: TUNNELS_STATISTICS_POLLING_FAILED.

SD-WAN Exception code: UPLINKS_POLLING_FAILED.

Exception message: Error converting value {null} to type 'System.Int32'. Path 'ifInfo[2].ifIndex', line 149, position 19.
Error converting value {null} to type 'System.Int32'. Path 'ifInfo[2].ifIndex', line 149, position 19.
Null object cannot be converted to a value type.

Product section

Orion Platform

Cause

This issue occurs due to ifIndex for some Aruba devices may be blank or null.  When this scenario occurs, SolarWinds ignores and drops the following data.

Resolution

To properly identify if the ifIndex is blank or null, utilize RestWalk and confirm if the ifIndex is blank or null.  Here is an example output of a problematic response:

 

"publicIp": "", "ifIndex": "", "comboPortSupported": "",

 

To resolve this issue, please upgrade to SolarWinds Platform 2024.4 and above.  There is no available workaround for this problem.