Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Cisco Nexus 7000 netflow - missing data


I've configured N7K to export layer 2 flows. Using 2 different flow collectors (open source and commercial), gaps/drops in the reported traffic are observed on a periodic basis.

Problem doesn't seems to be with the exporters, hence I wondering if netflow configuration on N7K can be tweaked to address this symptom.



Using the 'show exporter' command, no errors/drops are observed.

Here is my configuration:


flow record L2-Custom-Flow-Record

  match datalink mac source-address

  match datalink mac destination-address

  match datalink ethertype

  collect counter bytes

  collect counter packets

flow monitor TEST

  record L2-Custom-Flow-Record

  exporter FlOW-COLLECTOR

  exporter PLIXER

interface Ethernetx/y


  mac packet-classify

  layer2-switched flow monitor TEST input 

  no shutdown


switch: sh flow timeout

Flow timeout values

    Active timeout:           60 seconds

    Inactive timeout:         15 seconds

    Fast timeout:             Disabled

    Session aging timeout:    Disabled

    Aggressive aging timeout: Disabled


I'm using NX-OS 5.0(5)

Anybody know what's wrong?

Kerk Chun Sing

Everyone's tags (3)

Cisco Nexus 7000 netflow - missing data

Hi Kerk,

After exactly 30 minutes the drop occurs, I believe some process triggers on Monitoring tool which is causing this.

Did you try plotting the graph on some other monitoring tool?

It need not be a Nexus issue.

Check for logs on Nexus and on monitoring tool as well.

Are you getting the same kind of trend with graphs for other devices?

Warm Regards

Ameya Oke

New Member

Cisco Nexus 7000 netflow - missing data

Hi Ameya,

Yes, I've exported and graph on 2 different monitoring tools. It is shown in the white (pmacct/cacti) and black (Plixer Scrutinizer) background graphs. The Plixer folks couldn't figure out what could be the problem as well.

Kerk Chun Sing