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.

Netflow configure Cisco ASR 1002

We just installed a Cisco ASR 1002, The old net flow commands used in our 3845 do not work. Has anyone set configuration to export Top-Talkers?

Thanks

  • Hi Morang have you try the below configuration?

    flow record NETFLOW_RECORD

    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

    !

    !

    flow exporter NETFLOW_EXPORT

    destination X.X.X.X

    source FastEthernet0/1/0

    transport udp 2055

    export-protocol netflow-v5

    !

    !

    flow monitor NETFLOW_MONITOR

    description Original Netflow captures

    exporter NETFLOW_EXPORT

    cache timeout inactive 10

    cache timeout active 5

    record NETFLOW_RECORD

    interface GigabitEthernet0/0/4

    ip flow monitor NETFLOW_MONITOR input

  • Morang, Did you try the suggestions Lutherapalis suggested?

    We have just started trying to enable netflow export on an ASR 1001 - and it resulted in 99% memory being consumed almost immediately. Stopping export doesn't release memory, had to reload. I will suggest we try the above on our secondary ASR.

    Epenney

  • these configration were used on ASR1002-X,but error appeared as follow:

    ASR1002X(config-if)#ip flow monitor NETFLOW_MONITOR input

    Warning: Exporter netflow5-export could not be activated because: Invalid arguments provided.

    is there anyting else?

  • I have exactly the config on my ASR that lutherapalis​ sugguested above, but I am also getting the exact same error jeilian​ is getting.

    Has anyone solved this in any other way besides rebooting the router?

    This is on my primary WAN router and I really don't want to have to schedule a company-wide outage if I don't have to.