This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Setting up a 4510 with Sup 7-E

We've recently purchased a Cisco 4510 with the new 7E supervisor. We're running IOS XE 03.02.05.SG. We're running NTA 3.8.0.

This is the first device we have with the new style of doing netflow. I have the device showing up in NTA, but the graphs do not populate.

Does anyone have any ideas? Thanks,

Below is the config I've cobbled together from a few difference sources:

flow record orion-recorder

match ipv4 tos

match ipv4 protocol

match ipv4 source address

match ipv4 destination address

match transport source-port

match transport destination-port

collect transport tcp flags

collect interface output

collect counter bytes

collect counter packets

collect timestamp sys-uptime first

collect timestamp sys-uptime last

flow exporter orion

description netflow to solarwinds orion

destination 10.1.0.113

source Loopback0

transport udp 2055

export-protocol netflow-v5

template data timeout 60

option exporter-stats timeout 120

flow monitor monitor-orion

record orion-recorder

exporter orion

cache timeout inactive 30

cache timeout active 60

cache entries 1000

  • do a sh version and verify your license base.  LAN-Base will not support netflow according to Cisco. IP-Base is required.

    other items to check:

    - be sure the device is being monitored by npm (including the interface) and it is actively being managed.

    - be sure the configs point to the orion server as the netflow collector.

    - be sure UDP ports 161 and 2055 is allowed through your firewall.

  • Can you try the below changes:

    • Add: "match interface input" to the flow record
    • Change:
      • collect counter bytes to "collect counter bytes long"
      • collect counter packets to collect counter packets long
    •      Reduce the active cache timeout to 5 seconds from 60 seconds