We want to monitor NBAR2 on cisco C95xx device. We have already followed the instructions in the following KB article: Set up NBAR2 on Cisco devices
flow record xxxx match ipv4 tos match ipv4 protocol match ipv4 source address match ipv4 destination address match transport source-port match transport destination-port match interface input collect interface output collect counter bytes collect counter packets collect application nameexit
But we can't add the "collect application name" command, this is because this Cisco C95xx device doesn't have / support the "collect application name" command.
Below is an example of the NBAR configuration that we use on the Cisco C95xx device:
flow record NTArec match ipv4 version match ipv4 protocol match application name match connection client ipv4 address match connection server ipv4 address match connection server transport port match flow observation point collect flow direction collect connection initiator collect connection client counter packet long collect connection client counter bytes network long collect connection server counter packet long collect connection server counter bytes network long collect timestamp absolute first collect timestamp absolute last collect connection new-collectionsexit
When we check using Wireshark there is no application-id information as needed by SolarWinds to be able to monitor NBAR2, but we see there is Engine ID and Selector ID.
From the Cisco TAC try to run the configuration used on our customers and they can monitor the NBAR using Cisco Prime.
Has anyone had the same experience as ours and was finally able to monitor NBAR on a cisco C95xx device?
