Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Adtran node has two IP addresses used for SNMP and Netflow respectively

Adtran node has two IP addresses used for SNMP and Netflow respectively

Created by Daniel Polaske, last modified by MindTouch on Jun 23, 2016

Views: 1,345 Votes: 0 Revisions: 3

Overview

Rarely, a Netflow-configured device may be configured to send the bulk of its SNMP data with a particular source IP address, and the Netflow data with a different particular source IP address. When this occurs, NTA will be unable to break the Netflow down by the interface level as there are no interface index IDs available on the Netflow IP address.

In cases wherein the device is managed by an ISP or outside party, it may be difficult or impossible to change the device configuration to the required setup, which is to have the node report both SNMP and Netflow data with the same source IP address.  This allows the node to be managed in NPM, and then to be added as a Netflow source.

This appears to occur primarily to Adtran devices, however it is theoretically possible on other devices as well.

Environment

All NTA versions

All NPM versions

Cause 

NTA uses IfIndex to break down flow data into interfaces so that charts/graphs/reports can be broken down into conversations which traversed a particular interface, for example.  If a device has two IP addresses, one for SNMP and one for Netflow, the Netflow source can be added if there is a minimum of SNMP data available on that IP, but not enough to differentiate between different interface indexes on that node.  Therefore, the flow data can be viewed at the node level (under the Netflow Source "NTA Virtual Interface X" for example), but cannot be viewed per interface.

Resolution

There is a feature request pending review to be able to correlate two different NPM nodes with the same flow data, but until that is implemented, the only alternative is to configure the device to send SNMP and Netflow from the same management IP address.

 

Last modified

Tags

Classifications

Public