Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.


Home > Success Center > Netflow Traffic Analyzer (NTA) > NBAR2 and Flexible Netflow for Cisco WLC 5508

NBAR2 and Flexible Netflow for Cisco WLC 5508

Table of contents

Updated August 11, 2016


The Controller model and version (5508/ does not support the fields that Solarwinds is expecting to receive within the Netflow template, the 5508 Controllers using version 8.0 and above will only send the following data:

  • applicationTag (Application ID)
  • ipDiffServCodePoint (DSCP)
  • octetDeltaCount (Bytes)
  • packetDeltaCount (Packets)
  • postIpDiffServCodePoint (DSCP)
  • staIPv4Address (Client Source IP )
  • staMacAddress (Client Source MAC)
  • wlanSSID (WLAN ID)
  • wtpMacAddress (AP MAC)


All NTA versions


CISCO has come with a solution for this, in release 8.2 and above the WLC sends the following Netflow template for thrid-party monitoring tools like SolarWinds:

  • Application Tag
  • Client Mac Address
  • AP Mac address
  • WlanID
  • Source IP
  • Dest IP
  • Source Port
  • Dest Port
  • Protocol
  • Flow Start Time
  • Flow End Time
  • Direction
  • Packet count
  • Byte count
  • VLAN Id – Mgmt/Dyn
  • TOS - DSCP Value
  • Dot1x username


In version 8.2 data, SolarWinds is expected to receive, but there is a limitation for this that impacts the device because it does not allow this information to be sent to the Solarwinds server for the 5508 and this is the Controller model. Even though in 8.2, this information is sent  to the Netflow collectors, this is only supported by Controllers model 5520, 8510 and 8520; the Controllers that do not support this are 2500, 5508, 7500 and WiSM2.


Cisco provides 2 options:


  1. Upgrade your Controller hardware to 5520 running 8.2 and above.
  2. Look for a 3rd party Netflow collector that supports the 5508 Netflow template explained above.


As for now as long as your Solarwinds keeps expecting one format of Netflow template and the WLC is sending another there is not too much Cisco can do since this is a compatibility situation that goes beyond configuration.


See the following document and refer to Netflow Supprt in release 8.2:

Application Visibility and Control Feature Deployment Guide  (© 2016 Cisco, available at, obtained on August 11, 2016).​​​​​​​


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.




Last modified
23:37, 10 Aug 2016